SKILLEMALL.ai
GitHub ↗ RU Sign in

AC protocol-d-debugging

Guides systematic debugging through Protocol D (READ, ISOLATE, DOCS, HYPOTHESIZE, VERIFY). Use when junior says "stuck", "not working", "broken", "bug", "error", "crashed", "failing", "can't figure out", or expresses frustration. Do NOT use for general questions.

DanielPodolsky/ownyourcode Claude Code author: DanielPodolsky 1 file body ≈ 2 666 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Guides systematic debugging through Protocol D (READ, ISOLATE, DOCS, HYPOTHESIZE, VERIFY).

As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

AnalyzerSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
93
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Consistency w 8
40
the three weakest of ten parameters · all ten

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: 1. 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 60/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 40Consistency. Frontmatter name (protocol-d-debugging) differs from the folder (debugging)
    • 50When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 100Tools and files. No external tools needed
    • 100Steps. 35 steps
    • 100Execution cost. Instruction body is 2666 tokens
    • 100Running it twice. Mutating operations check current state
    • 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

    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 263: enough signal without eating the budget
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 35 items
    • +4Has examples (13 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.