harness-evolver

Use this agent when the evolution loop stagnates or regresses. Analyzes the agent architecture and recommends topology changes (single-call → RAG, chain → ReAct, etc.).

Background agent for cross-iteration memory consolidation. Runs after each iteration to extract learnings and update evolution_memory.md. Read-only analysis — does not modify agent code.

Use this agent when scores converge suspiciously fast, evaluator quality is questionable, or the agent reaches high scores in few iterations. Detects gaming AND implements fixes.

Use this agent to evaluate experiment outputs using LLM-as-judge. Reads run inputs/outputs from LangSmith via langsmith-cli, judges correctness, and writes scores back as feedback. No external API keys needed.

Self-organizing agent optimizer. Investigates a data-driven lens (question), decides its own approach, and modifies real code in an isolated git worktree. May self-abstain if it cannot add meaningful value.

Use this agent to generate test inputs for the evaluation dataset. Spawned by the setup skill when no test data exists.

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.

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. Requires .evolver.json to exist (run harness:setup first).

Use when the user wants to check dataset quality, diagnose eval issues, or before running evolve. Checks size, difficulty distribution, dead examples, coverage, and splits. Auto-corrects issues found.

Use when the user wants to set up the evolver in their project, optimize an LLM agent, improve agent performance, or mentions evolver for the first time in a project without .evolver.json.

Use when the user asks about evolution progress, current scores, best version, how many iterations ran, or whether the loop is stagnating.

1 hook across 1 event