AC systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ReferenceSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
The same skill appears in 1 more place: ClawHub
How to improve
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 59/100
- 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
- 30Running it twice. 5 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (systematic-debugging) differs from the folder (timeflow-systematic-debugging)
- 85Steps. 124 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 2430 tokens
- low 11 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)
- +3Description length 91: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 16 headings
- +3Step-by-step instructions: 124 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.
External checks
ClawHub: suspicious
This is a debugging guide, but it includes broad diagnostic guidance that could expose Mac keychain and code-signing identity details.
LLM: suspicious (high) · VirusTotal: · 29 May 2026