AB diagnose
Use when the user reports a hard bug, unexpected failure, or performance regression that needs root-cause analysis.
A discipline for hard bugs and regressions.
As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, running it twice
AnalyzerData and analyticsSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 110): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 7 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 57 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2522 tokens
- 100Progress reporting. Reports progress
- low 12 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 115: 120–800 characters recommended
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 24 headings
- +3Step-by-step instructions: 57 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.
External checks
ClawHub: clean
This skill is a bug-diagnosis workflow with a small human-input script, and I did not find hidden persistence, exfiltration, or privilege-seeking behavior.
LLM: benign (high) · VirusTotal: · 16 Sept 2026