AC systematic-debugging
Debug through a structured root-cause process instead of guesswork. Use when commands fail, tools behave unexpectedly, automations break, integrations only partially work, or the real cause is unclear.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureSoftware developmentInfrastructuretype 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 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
- 40Consistency. Frontmatter name (systematic-debugging) differs from the folder (jisang1000-systematic-debugging)
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Execution cost. Instruction body is 491 tokens
- 100Running it twice. No mutating operations
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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 201: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.
External checks
ClawHub: clean
This is an instruction-only debugging guide with no code or privileged behavior, though one example should be applied only in authorized contexts.
LLM: benign (high) · VirusTotal: · 29 May 2026