One-shot lifecycle command that chains init → baseline → spawn → eval → merge in a single invocation. Use when the user runs /hub:run or asks to execute a full AgentHub competition end-to-end.
71
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
—
The risk profile of this skill
Run the full AgentHub lifecycle in one command: initialize, capture baseline, spawn agents, evaluate results, and merge the winner.
/hub:run --task "Reduce p50 latency" --agents 3 \
--eval "pytest bench.py --json" --metric p50_ms --direction lower \
--template optimizer
/hub:run --task "Refactor auth module" --agents 2 --template refactorer
/hub:run --task "Cover untested utils" --agents 3 \
--eval "pytest --cov=utils --cov-report=json" --metric coverage_pct --direction higher \
--template test-writer
/hub:run --task "Write 3 email subject lines for spring sale campaign" --agents 3 --judge| Parameter | Required | Description |
|---|---|---|
--task | Yes | Task description for agents |
--agents | No | Number of parallel agents (default: 3) |
--eval | No | Eval command to measure results (skip for LLM judge mode) |
--metric | No | Metric name to extract from eval output (required if --eval given) |
--direction | No | lower or higher — which direction is better (required if --metric given) |
--template | No | Agent template: optimizer, refactorer, test-writer, bug-fixer |
Execute these steps sequentially:
Run /hub:hub-init with the provided arguments:
python {skill_path}/scripts/hub_init.py \
--task "{task}" --agents {N} \
[--eval "{eval_cmd}"] [--metric {metric}] [--direction {direction}]Display the session ID to the user.
If --eval was provided:
Baseline captured: {metric} = {value}baseline: {value} to .agenthub/sessions/{session-id}/config.yamlIf no --eval was provided, skip this step.
Run /hub:spawn with the session ID.
If --template was provided, use the template dispatch prompt from ../agenthub/references/agent-templates.md instead of the default dispatch prompt. Pass the eval command, metric, and baseline to the template variables.
Launch all agents in a single message with multiple Agent tool calls (true parallelism).
After spawning, inform the user that agents are running. When all agents complete (Agent tool returns results):
Run /hub:eval with the session ID:
--eval was provided: metric-based ranking with result_ranker.py--eval: LLM judge mode (coordinator reads diffs and ranks)If baseline was captured, pass --baseline {value} to result_ranker.py so deltas are shown.
Display the ranked results table.
Present the results to the user and ask for confirmation:
Agent-2 is the winner (128ms, -52ms from baseline).
Merge agent-2's branch? [Y/n]If confirmed, run /hub:merge. If declined, inform the user they can:
/hub:merge --agent agent-{N} to pick a different winner/hub:eval --judge to re-evaluate with LLM judge--template, agents use the default dispatch prompt from /hub:spawn19392f7
Also appears in
since Aug 28, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.