executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
evaluation-and-projectsPlan InternLM-XComposer benchmark workflows and related project package usage without executing downloads, judge calls, services, or long inference.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to plan, audit, or troubleshoot benchmark and related-project workflows for the InternLM-XComposer repository family without reopening the source checkout. It is intentionally non-executing: it preserves benchmark data layouts, command shapes, result files, submission expectations, and project-package routing, but it does not download benchmark data, launch models, call GPT/OpenAI judges, start services, or run long inference.
model-inference unless the request only asks for a non-executing ShareGPT4V/ShareCaptioner plan.omnilive. Keep only OmniLive benchmark planning here.finetuning. This sub-skill may mention ShareGPT4V installation and data layout, but not operate a training run.reward-model.Before producing a plan, identify:
references/benchmark-workflows.md for benchmark routing and data/result expectations.references/related-projects.md for ShareGPT4V and DualFocus installation, package routing, evaluation families, Captioner usage, and Slurm/local distinctions.references/data-conversion.md when the task involves JSONL, TSV, XLSX, answer-upload, or result-converter formats.references/troubleshooting.md when a plan is blocked by missing data, CUDA/Slurm, GPT judges, submission servers, output shape errors, or hardcoded source-era paths.python scripts/render_benchmark_plan.py --list
python scripts/render_benchmark_plan.py --workflow xcomposer2-mme --model-path <model> --data-root <data> --output-root <outputs> --gpus 1
python scripts/render_benchmark_plan.py --workflow sharegpt4v-eval --checkpoint share4v-7b --gpus 8 --format markdown
python scripts/render_benchmark_plan.py --workflow omnilive-video-mme --data-root <video-root> --gpus 8 --check-paths
The helper uses only Python's standard library, prints commands/checklists as text, and performs optional path-existence probes only when --check-paths is supplied.
A good response from this sub-skill names the chosen workflow, required data layout, GPU/Slurm and package requirements, non-executing command pattern, expected local result files, external submission/judge requirements, known blockers, and the sibling sub-skill to use if the user actually wants inference, service deployment, fine-tuning, or reward modeling.