BC skill-creator
[USM] Create new skills, modify and improve existing skills, measure skill performance, and manage skill distribution across Agents. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals, or when they ask to sync skills, manage the skill hub, or configure which agents can see which skills using the 2-layer 2-dimension architecture.
As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, consistency, 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: 21. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 2, column 20: description: [USM] Create new skills, modify and improve existing skills, measu… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
body-longSKILL.md body ≈ 8078 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (skill-creator) differs from the folder (skill-creator-usm)
- 40Execution cost. Instruction body is 8078 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. 79 steps, 4 vague phrases
- 70Failures and branches. 23 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 (12 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)
- -36 of 9 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 379: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 79 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.