BF doc-updates
Updates documentation after code changes with quality gates, slop detection, and accuracy checks. Use when code changes require corresponding doc updates.
Updates documentation after code changes with quality gates, slop detection, and accuracy checks.
As a process F 38/100 · Will not run — References files that are not bundled: ../plugins/{plugin}.md
Runs in: Hermes Agent
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 154 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: ../plugins/{plugin}.md - note
frontmatter-keyunknown frontmatter key "alwaysApply" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "complexity" - note
frontmatter-keyunknown frontmatter key "model_hint" - note
frontmatter-keyunknown frontmatter key "estimated_tokens" - note
frontmatter-keyunknown frontmatter key "progressive_loading" - note
frontmatter-keyunknown frontmatter key "modules" - note
frontmatter-keyunknown frontmatter key "dependencies" - note
frontmatter-keyunknown frontmatter key "optional_dependencies"
Process rating: all ten parameters 38/100
Will not run. References files that are not bundled: ../plugins/{plugin}.md
- 0Tools and files. 1 referenced file(s) missing: ../plugins/{plugin}.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 94 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3608 tokens
- 100Running it twice. Mutating operations check current state
- low 16 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 154: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 94 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.