BF fix
User behavior correction skill. Triggered by "fix:" prefix feedback (e.g., "fix: why didn't you commit?"). Analyzes the mistake, improves the relevant prompt (skill/rule/agent/memory/hook) to prevent recurrence, then fixes the current issue. TodoWrite required for all steps. Use when "fix:", "fix this", "correct", "why not", "why missing", "behavior fix" is mentioned.
As a process F 47/100 · Will not run — References files that are not bundled: ../fa/SKILL.md
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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9658 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../fa/SKILL.md - note
frontmatter-keyunknown frontmatter key "depends-on"
Process rating: all ten parameters 47/100
- 0Tools and files. 1 referenced file(s) missing: ../fa/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 9658 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 100Steps. 86 steps
- 100Failures and branches. 9 branches, has a failure section
- 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 (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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 370: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 86 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.