BB complete-implementation
Use when all tasks for a feature are marked COMPLETE — runs holistic quality gates including code review, feature verification, integration check, documentation drift audit and update, and context refinement. Creates follow-up plans when issues are found.
Use when all tasks for a feature are marked COMPLETE — runs holistic quality gates including code review, feature verification, integration check…
As a process B 71/100 · Nearly there — weak spots: result and completion, when it triggers, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 7919 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 71/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 7919 tokens
- 100Steps. 19 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- low 18 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
- +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 255: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (32 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.