BC skill-creator
Creates new skills, modifies and improves existing skills, and measures skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Creates new skills, modifies and improves existing skills, and measures skill performance.
As a process C 62/100 · Has gaps — weak spots: inputs and preconditions, execution cost
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: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8297 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 188): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 62/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 8297 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Steps. 78 steps, 8 vague phrases
- 60Failures and branches. 2 branches
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (10 tags): a typed call is more reliable
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)
- -35 of 9 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 325: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 78 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.