Skip to content
Back to skills

Evaluation Workflows

ASecurity

"Run, resume, dry-run, and debug OpenCompass evaluation jobs from

  • 247 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 8, 2026
toolsapibackend

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill evaluation-workflows --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Evaluation Workflows?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Evaluation Workflows
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-evaluation-workflows-36b37e62/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-evaluation-workflows-36b37e62)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: evaluation-workflows
description: "Run, resume, dry-run, and debug OpenCompass evaluation jobs from
  the installed opencompass CLI or config-defined runner workflows."
disable-model-invocation: true
metadata:
  disco-role: operating
license: Apache 2.0
---

# Evaluation Workflows

Use this sub-skill when an agent needs to launch or debug OpenCompass evaluation execution: planning a run, choosing `--mode`, using `--debug` or `--dry-run`, resuming with `--reuse`, selecting local/Slurm/DLC orchestration, or checking whether the installed CLI is available.

## Route Here For

- Running `opencompass` from a config file or from `--models` / `--datasets` shortcuts.
- Safe first-run checks with `--debug`, `--dry-run`, explicit `--work-dir`, and small dataset/model selections.
- Resuming a failed run from a previous `work_dir` timestamp with `--mode eval`, `--mode viz`, and `--reuse`.
- Choosing local, Slurm, or DLC execution and understanding how partitioners produce tasks for runners.
- Creating native verification candidates that exercise CLI construction without requiring model downloads, GPU execution, or credentials.

## Route Elsewhere

- Config inheritance, model/dataset lists, custom datasets, and config authoring belong in `../configuration-and-datasets/SKILL.md`.
- HuggingFace/API/vLLM/LMDeploy adapter details and backend installation choices belong in `../model-backends/SKILL.md`.
- Prompt templates, retrievers, inferencers, and OpenICL internals belong in `../prompt-and-inference/SKILL.md`.
- Summarizer customization, result table interpretation, and repeat-analysis outputs belong in `../results-and-analysis/SKILL.md`.

## Start Here

1. Prefer the installed CLI entrypoint: `opencompass`, not a source-checkout script dependency.
2. For a new config, start with a sequential sanity run: `opencompass path/to/eval_config.py --debug -w outputs/smoke`.
3. To inspect task planning without running model jobs, add `--dry-run`; this implies debug behavior and returns before runner execution.
4. For a complete run, use `opencompass path/to/eval_config.py -w outputs/experiment --mode all`.
5. If inference already exists, rerun downstream stages with `--mode eval --reuse` or `--mode viz --reuse` and the same `--work-dir`.

## References

- `references/cli-workflows.md`: command patterns for configure -> inference -> evaluation -> visualization, dry runs, debug runs, reuse, and work directory handling.
- `references/runners-and-partitioners.md`: how local, Slurm, and DLC runners interact with partitioners and task types.
- `references/troubleshooting.md`: common execution failures and safe diagnosis steps.
- `scripts/opencompass_cli_smoke.py`: safe CLI help/argument smoke check that does not run models.

## Safety Notes

- Do not claim that real HuggingFace model inference was verified unless the target environment has compatible model/runtime dependencies and the run actually completed.
- Optional execution backends such as vLLM, LMDeploy, DLC, and API extras may require additional packages or credentials; keep those checks separate from CLI smoke validation.
- Treat `--hf-num-gpus` as the minimum required GPU count used for scheduling/allocation, not as proof that OpenCompass will consume exactly that many GPUs.

Files in this skill

  • SKILL.md3.2 KB
  • references/cli-workflows.md5.5 KB
  • references/runners-and-partitioners.md5.4 KB
  • references/troubleshooting.md5.5 KB
  • scripts/opencompass_cli_smoke.py2.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.