AB muse
Defining and managing design tokens, applying token systems to existing codebases, building design system foundations. Use for spacing, color, typography, dark mode, cross-platform output.
Defining and managing design tokens, applying token systems to existing codebases, building design system foundations.
As a process B 73/100 · Nearly there — weak spots: when it triggers, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5902 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 192): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 73/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5902 tokens
- 85Steps. 89 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 14 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 188: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 89 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (13 of 13)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.