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 asks about evolution progress, current scores, best version, how many iterations ran, or whether the loop is stagnating.
Claude Code
$ npx -y skills add raphaelchristi/harness-evolver --skill status --agent claude-code
Codex
$ npx skills add raphaelchristi/harness-evolver --skill status -a codex -y
Cursor
$ npx skills add raphaelchristi/harness-evolver --skill status -a cursor -y
Gemini CLI
$ npx skills add raphaelchristi/harness-evolver --skill status -a gemini-cli -y
GitHub Copilot
$ npx skills add raphaelchristi/harness-evolver --skill status -a github-copilot -y
OpenCode
$ npx skills add raphaelchristi/harness-evolver --skill status -a opencode -y
Windsurf
$ npx skills add raphaelchristi/harness-evolver --skill status -a windsurf -y
name: harness:status description: "Use when the user asks about evolution progress, current scores, best version, how many iterations ran, or whether the loop is stagnating." allowed-tools: [Read, Bash]
Show current evolution progress.
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")}"$EVOLVER_PY $TOOLS/evolution_chart.py --config .evolver.json
After displaying the chart:
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 wants to verify that the evolved agent's score is stable and reliable. Runs evaluation multiple times and…
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.…
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.