SKILLEMALL.ai

BC snapback

Diagnose why an AI-agent run failed and get a structured fix — and catch failures live, mid-run, before they burn your budget. Use this skill WHENEVER an agent run loops, stalls, hits a step/token/context limit, returns the wrong output, or fails and you want to know WHY and HOW to fix it. Also use it DURING a run: detect_loop and budget_guard catch a runaway before the step limit; a live session streams your steps and warns you in real time. Triggers: "why did my agent fail", "it keeps looping", "diagnose this run", "the agent repeated the same tool call", "hit the step limit", "running out of context", "burning tokens", "wrong output", "detect a loop", "watch my run", "check my agent before running". Connects over MCP; most tools are free (discovery, docs, loop + budget checks, live sessions, and instant infrastructure-error diagnosis across 46 families), diagnosis is metered (token or pay-per-call via x402 on Solana or EVM — no account needed).

ClawHub Agent Skills author: ra1labsworkx-wq v1.8.4 MIT-0 5 files body ≈ 3 512 tokens Open the sourceclawhub.ai↗ analyzed 7 d ago

Diagnose why an AI-agent run failed and get a structured fix — and catch failures live, mid-run, before they burn your budget.

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

AnalyzerGitHubAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
C
50/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: 5. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "homepage"

    Process rating: all ten parameters 50/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. 7 mutating operations with no state check
    • 40Consistency. Frontmatter name (snapback) differs from the folder (snapback-selfheal)
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 12 steps
    • 100Execution cost. Instruction body is 3512 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Description length 961: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +5Description quotes 11 example trigger phrases
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 12 items
    • +4Has examples (8 code blocks)
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This skill appears purpose-built for agent failure diagnosis, but it asks users to send sensitive run details to a remote service and optionally install an auto-healing Python interceptor that is under-described in the package.
    LLM: suspicious (high) · VirusTotal: · 2 Oct 2026