SKILLEMALL.ai

AC deep-debugging

Evidence-first debugging and incident triage for unclear, recurring, production-like, or high-risk software bugs. Use when the user asks for root cause analysis, says a fix did not work, reports 401/403/500 with context, deploy/runtime failures, broken integrations, or needs investigation before code changes. Do not use for obvious typos, missing installs, or trivial one-line fixes.

ClawHub Agent Skills author: brasco05 v2.2.0 MIT-0 8 files · 1 script body ≈ 1 376 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

IntegrationSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
92
Run on models
none yet
Process rating
C
63/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
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: 8. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "requiredEnv"
    • note frontmatter-key unknown frontmatter key "permissions"
    • note frontmatter-key unknown frontmatter key "security"

    Process rating: all ten parameters 63/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
    • 30Running it twice. 1 mutating operations with no state check
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 100Steps. 24 steps
    • 100When it triggers. States when to use and when not to
    • 100Failures and branches. 4 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1376 tokens
    • 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
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 385: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 24 items
    • +4Has examples (9 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +3All 1 scripts are documented

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

    External checks

    ClawHub: clean
    This is a disclosed read-only debugging and incident-triage skill with an optional local snapshot helper that avoids printing secret values.
    LLM: benign (high) · VirusTotal: · 29 May 2026