mcpField
S
skill-optimizer

skill-optimizer

github.com/mcollinaAgent workflows2.0k1.4k installsUpdated 1w ago
Repository

About skill-optimizer

A skill for evaluating and improving how reliably models apply other skills. It uses benchmark comparisons, failure analysis, targeted edits, and release gates to track behavior and regressions.

Key features

  1. 01Measures skill-on and baseline behavior
  2. 02Classifies failures and regressions
  3. 03Refines triggers and examples
  4. 04Compares evaluation results
  5. 05Defines release guardrails

Use cases

  1. 01Diagnosing criteria that models consistently miss
  2. 02Improving skill retrieval under context limits
  3. 03Checking whether a skill worsens outputs
  4. 04Setting evaluation gates for skill updates

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mcollina/skills --skill skill-optimizer

After installing, type/skill-optimizerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

tile.json
rules/
activation-design.md
benchmark-loop.md
context-budget.md
regression-triage.md
release-gates.md

Details

From the project README

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:

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

Comments

Markdown supported