skill optimizer
- Repo stars 1,812
- Author repo skills
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @mcollina · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
## 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
Sections and files
Listed in source order.
sections -> When to use → Optimization loop (default workflow) → How to use → Practical heuristics
terms -> Measure baseline and skill-on behavior · Find failure pattern · Edit for salience · Re-run evals · Ship with guardrails · few high-signal rules · top-level checklists · integrated example
files/cmd -> rules/benchmark-loop.md · rules/activation-design.md · rules/context-budget.md · rules/regression-triage.md · rules/release-gates.md · Go/no-go · gains/losses
body sha256 -> ce9b4b444e15
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
Optimization loop (default workflow)
Measure baseline and skill-on behavior (per model, per scenario, per criterion) Find failure pattern: universal failure (0% with skill) model-specific weakness regression (negative delta)
How to use
Read individual rule files for detailed procedures and templates: rules/benchmark-loop.md - End-to-end benchmark loop and scoring rules/activation-design.md - Improve retrieval and instruction uptake rules/context-budget.md - Reduce token cost without losing behavior rules/regression-triage.md - Diagnose and fix skill-on regressions
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