BF skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, 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.
As a process F 48/100 · Will not run — References files that are not bundled: references/schemas.md, assets/eval_review.html
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8157 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/schemas.md - warning
missing-refreference to a missing file: assets/eval_review.html
Process rating: all ten parameters 48/100
- 0Tools and files. 2 referenced file(s) missing: references/schemas.md, assets/eval_review.html
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (skill-creator) differs from the folder (rex-skill-creator)
- 40Execution cost. Instruction body is 8157 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Steps. 80 steps, 4 vague phrases
- 70Failures and branches. 24 branches
- 100Result and completion. Output format and completion criterion are stated
- 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 (9 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)
- -42 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 3 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 319: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 80 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.