skill-optimizer — Claude Code skill: tune skills, run benchmarks
A skill for people who write and edit skills: it shows why a model ignores yours and whether it makes output worse.
npx skills add mcollina/skills --skill skill-optimizer -a claude-codeWhat skill-optimizer does
skill-optimizer runs an optimization loop over your skills. You measure baseline and skill-on behavior per model, per scenario, per criterion. Then you classify the failure: the skill never fires, one model lags, or the delta goes negative. Edits target salience — explicit triggers, concrete integrated examples, tighter checklists and decision rules. Re-run the evals, compare deltas, ship with a documented gate, run history and follow-up issues.
Five rule files carry the detail: rules/benchmark-loop.md for the end-to-end loop and scoring, rules/activation-design.md for retrieval and instruction uptake, rules/context-budget.md for cutting token cost, rules/regression-triage.md for diagnosing regressions and rules/release-gates.md for go/no-go criteria. The heuristics are blunt: a few high-signal rules beat many soft recommendations, fragile behavior belongs in top-level checklists, every common scenario needs at least one integrated example, and what must not be omitted needs its own wording.
The skill does not run evals for you. Scenarios and scoring are your job; it supplies the procedure and templates. Without a way to compare output with and without the skill, the loop degrades into guessing at wording. Set up a repeatable run first, then touch the text.
What it helps with
- find out why a model ignores your skill
- separate a universal failure from one model's weakness
- catch a regression caused by the skill itself
- shrink skill context without losing behavior
- set a release gate for skill updates
Example prompts for the agent
- run the skill benchmark and show me the with-skill vs without-skill delta
- why does this criterion fail across every model?
- cut the skill's context cost and check the behavior still holds
How to install skill-optimizer
1Skills CLI (Vercel)
npx skills add mcollina/skills --skill skill-optimizer -a claude-code2Manually: put the files in place
~/.claude/skills/skill-optimizer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/skill-optimizer/
1Skills CLI (Vercel)
npx skills add mcollina/skills --skill skill-optimizer -a codex2Manually: put the files in place
.agents/skills/skill-optimizer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mcollina/skills --skill skill-optimizer -a cursor2Manually: put the files in place
.cursor/skills/skill-optimizer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mcollina/skills skill-optimizer2Manually: put the files in place
.github/skills/skill-optimizer/SKILL.md1Skills CLI (Vercel)
npx skills add mcollina/skills --skill skill-optimizer -a gemini-cli2Platform CLI
gemini skills install https://github.com/mcollina/skills --path skills/skill-optimizerManually: put the files in place
.devin/skills/skill-optimizer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mcollina/skills --skill skill-optimizer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about skill-optimizer
How do I install skill-optimizer in Claude?
Run npx skills add mcollina/skills --skill skill-optimizer -a claude-code. The skill file lands at ~/.claude/skills/skill-optimizer/SKILL.md.
What does skill-optimizer do?
It lays out a loop for improving skills: measure baseline and skill-on behavior, classify the failure pattern, edit for salience, re-run evals and ship behind a gate. Five rule files hold the procedures and templates.
Do I need my own evals for it to work?
Yes. The skill provides the procedure and templates; you build the scenarios and scoring. Without a with-skill vs without-skill comparison, edits to the text are guesswork.
Source text
SKILL.md · MIT
--- name: skill-optimizer description: "Optimizes AI skills for activation, clarity, and cross-model reliability. Use when creating or editing skill packs, diagnosing weak skill uptake, reducing regressions, tuning instruction salience, improving examples, shrinking context cost, or setting benchmark/release gates for skills. Trigger terms: skill optimization, activation gap, benchmark skill, with/without skill delta, regression, context budget, prompt salience." metadata: tags: skills, optimization, benchmarking, activation, regressions, prompt-engineering --- ## When to use Use this skill when you need to: - Improve whether a skill is actually applied by models - Diagnose why some criteria fail across all models - Prevent a skill from making outputs worse - Refactor skill text for stronger retrieval under context pressure - Build repeatable benchmark loops and release gates ## Optimization loop (default workflow) 1. **Measure baseline and skill-on behavior** (per model, per scenario, per criterion) 2. **Find failure pattern**: - universal failure (0% with skill) - model-specific weakness - regression (negative delta) 3. **Edit for salience**: - add explicit triggers - add concrete integrated examples - tighten checklists and decision rules 4. **Re-run evals** and compare deltas 5. **Ship with guardrails** (documented gate + run history + follow-up issues) ## How to use Read individual rule files for detailed procedures and templates: - [rules/benchmark-loop.md](rules/benchmark-loop.md) - End-to-end benchmark loop and scoring - [rules/activation-design.md](rules/activation-design.md) - Improve retrieval and instruction uptake - [rules/context-budget.md](rules/context-budget.md) - Reduce token cost without losing behavior - [rules/regression-triage.md](rules/regression-triage.md) - Diagnose and fix skill-on regressions - [rules/release-gates.md](rules/release-gates.md) - Go/no-go criteria before shipping skill updates ## Practical heuristics - Prefer **few high-signal rules** over many soft recommendations - Put fragile, high-value behaviors in **top-level checklists** - Include at least one **integrated example** per common scenario - Add explicit wording for what must **not** be omitted - Track gains/losses with **with-skill vs without-skill** comparisons
© mcollina · MIT · mcollina/skills