Skip to content
Back to skills

Evolve Skill

ASecurity

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.

  • 274 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added October 25, 2026
developmentgobash

Security analysis

A100/100

Scanned October 25, 2026

npx -y skills add danielvm-git/bigpowers --skill evolve-skill --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Evolve Skill?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Evolve Skill
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/danielvm-git-evolve-skill-bigpowers/badge)](https://www.skillsdirectory.com/skills/danielvm-git-evolve-skill-bigpowers)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: evolve-skill
model: opus
description: "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."
disable-model-invocation: true
---

<!-- 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](REFERENCE.md) for ADR template.


<!-- story: e31s07 -->

---

# Evolve Skill — ADR snippet

```markdown
## ADR-XXXX: Evolve &lt;skill-name&gt;

**Status:** Accepted
**Benchmark:** before X% / after Y%
**Change:** one-sentence summary
**Evidence:** path/to/benchmark-report.md
```

Benchmark repo: `bigpowers-benchmark` — resolve the local clone on this machine; clone it from wherever your fork lives if absent. Never assume a hard-coded absolute path or a specific owner.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.