BF subagent-driven-development
Gunakan saat ada rencana implementasi dengan tugas yang sebagian besar independen dan ingin dieksekusi via subagent paralel di sesi yang sama (bukan context switch). Aktif saat user minta "jalankan plan pakai subagent", "dispatch implementer per task", atau "subagent-driven dev"." [shape=box];; plans" [shape=box];. Aktif untuk tugas terkait skill ini.
As a process F 41/100 · Will not run — References files that are not bundled: ../requesting-code-review/code-reviewer.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: 7. 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 204: …ontext switch). Aktif saat user minta "jalankan plan pakai subagent", "dispatc… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
body-longSKILL.md body ≈ 7747 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../requesting-code-review/code-reviewer.md
Process rating: all ten parameters 41/100
- 0Tools and files. 1 referenced file(s) missing: ../requesting-code-review/code-reviewer.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 23 mutating operations with no state check
- 70Execution cost. Instruction body is 7747 tokens
- 85Steps. 43 steps, 1 vague phrases
- 100Failures and branches. 12 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 30 top-level sections: this looks like several domains in one skill
- 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
- +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
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 353: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.