AC proof-loop
Run evidence-gated coding sprints with frozen ACs, separated builder/verifier roles, and durable proof artifacts.
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
AnalyzerSoftware developmentInfrastructureOperations and projectstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 31. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 70When it triggers. States when to use, but not when not to
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 822 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 113: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 8 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (4 of 5)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.
External checks
ClawHub: clean
This skill is a repo-local proof workflow that writes disclosed task artifacts and runs local checks in ways that match its stated purpose.
LLM: benign (high) · VirusTotal: · 1 Sept 2026