BF update-project-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions documentation updates in any project. Provides a guided workflow for updating project documentation based on code changes.
As a process F 61/100 · Will not run — References files that are not bundled: /getting-started/installation.md, /getting-started/quick-start.md, /guides/basic-usage.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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 7741 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: /getting-started/installation.md - warning
missing-refreference to a missing file: /getting-started/quick-start.md - warning
missing-refreference to a missing file: /guides/basic-usage.md - warning
missing-refreference to a missing file: /api/index.md
Process rating: all ten parameters 61/100
- 0Tools and files. 4 referenced file(s) missing: /getting-started/installation.md, /getting-started/quick-start.md, /guides/basic-usage.md
- 0Result and completion. Does not say what the result is
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 7741 tokens
- 85Steps. 140 steps, 2 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 10 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 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 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
- +1No license
- +2Single-language instructions
- +5Description quotes 10 example trigger phrases
- +3Description length 461: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 140 items
- +4Has examples (15 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.