dev-dry-run
Use when the user wants to smoke-test the evolve pipeline, test tools, or verify the plugin works end-to-end. Also use when the…
Use when the user wants to verify that the evolved agent's score is stable and reliable. Runs evaluation multiple times and reports mean ± std.
Claude Code
$ npx -y skills add raphaelchristi/harness-evolver --skill certify --agent claude-code
Codex
$ npx skills add raphaelchristi/harness-evolver --skill certify -a codex -y
Cursor
$ npx skills add raphaelchristi/harness-evolver --skill certify -a cursor -y
Gemini CLI
$ npx skills add raphaelchristi/harness-evolver --skill certify -a gemini-cli -y
GitHub Copilot
$ npx skills add raphaelchristi/harness-evolver --skill certify -a github-copilot -y
OpenCode
$ npx skills add raphaelchristi/harness-evolver --skill certify -a opencode -y
Windsurf
$ npx skills add raphaelchristi/harness-evolver --skill certify -a windsurf -y
name: harness:certify description: "Use when the user wants to verify that the evolved agent's score is stable and reliable. Runs evaluation multiple times and reports mean ± std." allowed-tools: [Read, Bash, Glob]
Verify score stability by running evaluation multiple times and reporting statistical confidence.
TOOLS="${EVOLVER_TOOLS:-$([ -d ".evolver/tools" ] && echo ".evolver/tools" || echo "$HOME/.evolver/tools")}"
EVOLVER_PY="${EVOLVER_PY:-$([ -f "$HOME/.evolver/venv/bin/python" ] && echo "$HOME/.evolver/venv/bin/python" || echo "python3")}"Read `.evolver.json` to get the best experiment and dataset.
Run evaluation 3 times on the current code (not a worktree — the best code is already merged):
for i in 1 2 3; do
$EVOLVER_PY $TOOLS/run_eval.py \
--config .evolver.json \
--worktree-path "." \
--experiment-prefix "certify-run-$i"
doneAfter all 3 runs complete, read results and compute statistics:
$EVOLVER_PY $TOOLS/read_results.py --experiments "certify-run-1-{suffix},certify-run-2-{suffix},certify-run-3-{suffix}" --config .evolver.json --format summaryCalculate mean and standard deviation from the 3 combined_scores.
CERTIFICATION REPORT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Runs: 3
Mean: {mean:.3f}
Std: {std:.3f}
Range: {min:.3f} — {max:.3f}
Verdict: {STABLE|UNSTABLE}**STABLE** (std < 0.05): Score is reliable. The agent performs consistently.
**MARGINAL** (0.05 <= std < 0.10): Score varies moderately. Consider adding rubrics to reduce judge variance.
**UNSTABLE** (std >= 0.10): Score is unreliable. The LLM judge interprets criteria differently across runs. Add few-shot examples or tighter rubrics.
If STABLE: suggest `/harness:deploy` to finalize. If UNSTABLE: suggest adding rubrics to dataset examples, or running `/harness:evolve` with `heavy` mode for more thorough evaluation.
Point at any LLM agent codebase. Harness Evolver will autonomously improve it — prompts, routing, tools, architecture — using multi-agent evolution with LangSmith as the evaluation backend.
Use when the user wants to smoke-test the evolve pipeline, test tools, or verify the plugin works end-to-end. Also use when the…
Use when the user wants to release a new version, publish to npm, create a GitHub release, bump version, or tag a release. Also…
Use when the user wants to validate the plugin, check integrity, verify cross-references, or before a release. Also use when the…
Use when the user is done evolving and wants to finalize, clean up, tag the result, or push the optimized agent.
Use when the user wants to run the optimization loop, improve agent performance, evolve the agent, or iterate on quality.…
Use when the user wants to check dataset quality, diagnose eval issues, or before running evolve. Checks size, difficulty…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.