BF writing-skills
Gunakan saat ingin membuat/memperbaiki skill (process documentation) dengan pendekatan Test-Driven Development: tulis skenario pressure, lihat agen gagal tanpa skill, tulis skill, verifikasi agen patuh. Aktif saat user minta "buat skill", "skill creation TDD", atau "authoring skill".
As a process F 50/100 · Will not run — References files that are not bundled: ../using-superpowers/references/codex-tools.md, ../using-superpowers/references/gemini-tools.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: 9. 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 241: …asi agen patuh. Aktif saat user minta "buat skill", "skill creation TDD", atau… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
body-longSKILL.md body ≈ 7322 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../using-superpowers/references/codex-tools.md - warning
missing-refreference to a missing file: ../using-superpowers/references/gemini-tools.md
Process rating: all ten parameters 50/100
- 0Tools and files. 2 referenced file(s) missing: ../using-superpowers/references/codex-tools.md, ../using-superpowers/references/gemini-tools.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 26 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 7322 tokens
- 85Steps. 142 steps, 1 vague phrases
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 42 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
- +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
- -215 emoji in the instructions: noise for the model
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 284: enough signal without eating the budget
- +4Structure: 72 headings
- +3Step-by-step instructions: 142 items
- +4Has examples (21 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 50.