BC clarify-docs
TRIGGER when: asked to clarify or improve the explanation in existing local human documentation, such as a guide, design document, or implementation plan. Grounds edits in requirements and source while preserving technical meaning. Not for code, config, generic response brevity, PR drafts, or agent instructions. Explicit instruction or SKILL.md targets receive a /kk:implement suggestion without edits or automatic handoff.
TRIGGER when: asked to clarify or improve the explanation in existing local human documentation, such as a guide, design document, or implementation plan.
As a process C 63/100 · Has gaps — weak spots: result and completion, failures and branches, consistency
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 63/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (clarify-docs) differs from the folder (instructions)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 6 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 592 tokens
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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 425: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 6 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.