AF skill-builder
Builds lean SKILL.md-based skills: decides when a skill is justified, drafts a minimal skill skeleton, and audits existing skills for bloat and drift. Use when creating a new skill, tightening an existing one, or deciding whether the right answer is a plain edit, an existing tool, or a subagent instead. Also use when reviewing a skill's trigger description, restructuring a bloated SKILL.md, or moving detail into references. Even if the user just says "should this be a skill?" or "this skill feels too big," use this.
As a process F 46/100 · Will not run — References files that are not bundled: references/checklist.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/checklist.md
Process rating: all ten parameters 46/100
- 0Tools and files. 1 referenced file(s) missing: references/checklist.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (skill-builder) differs from the folder (lean-skill-builder)
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 100Steps. 64 steps
- 100Execution cost. Instruction body is 1492 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 521: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 64 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.