SKILLEMALL.ai
GitHub ↗ RU Sign in

AB taku-debug

When the user reports a bug, crash, error, or anything that is broken or behaving unexpectedly, invoke this skill FIRST — before writing any code or proposing any fix. This skill is the mandatory entry point for ALL bug-fix tasks. The user expects you to investigate root cause systematically before fixing. Without this skill, you will likely fix the symptom instead of the cause, which is the #1 debugging failure mode. Use this skill whenever the user says anything like: "fix this bug", "crashes", "returns null", "500 error", "not working", "wrong result", "throws exception", "timeout", "silent failure", "was working yesterday", "broke after deploy", "sometimes fails", "only in production", "works locally but not in CI/staging", "CLI crashes", "config missing", "test fails", or describes any error/stack trace. Also: "调试", "找bug", "报错", "排查问题", "不工作了", "挂了", "崩了", "数据不对". Do NOT use for: lint fixes, dependency updates, adding features, refactoring, or any task that is NOT about fixing broken behavior.

ClawHub Agent Skills author: KennyWu v1.0.0 MIT-0 3 files body ≈ 3 003 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process B 78/100 · Nearly there — weak spots: inputs and preconditions, running it twice

AnalyzerSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
93
Run on models
none yet
Process rating
B
78/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
Result and completion w 14
60
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: 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 78/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 6 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70Failures and branches. 10 branches
    • 100Tools and files. No external tools needed
    • 100Steps. 40 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3003 tokens
    • 100Progress reporting. Reports progress

    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

    • +3Description length 1014: 120–800 characters recommended
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 17 example trigger phrases
    • +4Description says when NOT to use the skill
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 40 items
    • +3Output format is stated explicitly
    • +4Has examples (3 code blocks)

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

    External checks

    ClawHub: clean
    Taku Debug is an instruction-only debugging workflow with disclosed, purpose-aligned guidance and no executable code or hidden install behavior.
    LLM: benign (high) · VirusTotal: · 29 May 2026