agentleFS
danielvm-gitdanielvm-git/bigpowers/skills/evolve-skill/SKILL.md

evolve-skill

Skill288 starsChanged 7 days agoMITView on GitHub

Benchmark-gated skill evolution — consume bigpowers-benchmark report, propose plan-work change, edit skill via craft-skill, re-run benchmark, record ADR. Use when a skill underperforms on benchmark or stocktake finds systemic gap.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md
<!-- story: e23s03 --><!-- story: e09s01 --><!-- story: e09s05 -->

Evolve Skill

HARD GATE — No skill change ships without benchmark score ≥ pre-change baseline. Learning is measured and versioned — never implicit.

Loop

  1. Regression gate — Run bash scripts/run-verification-gates.sh to catch mechanical regressions (compliance, sync pipeline, size budget) before spending time on benchmark evals. If golden suite fails, fix regressions first — they are pre-requisites for any capability improvement.
  2. Establish baseline — Run run-benchmark <skill> --baseline. If no definition exists at specs/benchmarks/<skill>.yaml, create one following specs/benchmarks/SCHEMA.md first. Save report path in state.yaml. If specs/benchmarks/reports/BASELINE-<skill>.yaml already exists, skip this step.
  3. Identify gap — Read the baseline report (specs/benchmarks/reports/BASELINE-<skill>.yaml). Find scenarios with result: FAIL or low pass_at_k. This is the measurable gap.
  4. plan-work — Write a minimal change proposal targeting the failing scenarios. Include verify commands.
  5. Edit via craft-skill / direct SKILL.md edit; run bash scripts/sync-skills.sh.
  6. Re-run benchmark — run-benchmark <skill>. Compare new pass_at_k against baseline.
    • IMPROVED or STABLE → advance to step 6.
    • REGRESSION (new pass_at_k < baseline) → revert the change and loop back to step 3.
  7. Record decision — Write specs/adr/NNNN-evolve-<skill>.md with before/after pass_at_k scores. Update session-state.

Verify

→ verify: test -d specs/benchmarks && test -f skills/run-benchmark/SKILL.md

See REFERENCE.md for ADR template.

<!-- story: e31s07 -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.