协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
evaluation-workflows【开发与工程】Run, resume, dry-run, and debug OpenCompass evaluation jobs from the installed opencompass CLI or config-defined runner workflows.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
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.
opencompass from a config file or from --models / --datasets shortcuts.--debug, --dry-run, explicit --work-dir, and small dataset/model selections.work_dir timestamp with --mode eval, --mode viz, and --reuse.../configuration-and-datasets/SKILL.md.../model-backends/SKILL.md.../prompt-and-inference/SKILL.md.../results-and-analysis/SKILL.md.opencompass, not a source-checkout script dependency.opencompass path/to/eval_config.py --debug -w outputs/smoke.--dry-run; this implies debug behavior and returns before runner execution.opencompass path/to/eval_config.py -w outputs/experiment --mode all.--mode eval --reuse or --mode viz --reuse and the same --work-dir.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.--hf-num-gpus as the minimum required GPU count used for scheduling/allocation, not as proof that OpenCompass will consume exactly that many GPUs.