SKILLEMALL.ai
GitHub ↗ RU Sign in

BB error-scan

Scan recent Claude Code activity for errors and failure signals across all sessions using Agent Monitor data — APIError events and PreToolUse→PostToolUse gaps (tools that started but never completed) — then group failures by tool and model and rank them by frequency. Use when checking for errors or asking "what's failing right now".

hoangsonww/Claude-Code-Agent-Monitor Agent Skills author: hoangsonww 2 files body ≈ 660 tokens Open the sourcegithub.com↗ analyzed 26 h ago

Scan recent Claude Code activity for errors and failure signals across all sessions using Agent Monitor data — APIError events and PreToolUse→PostToolUse gaps…

As a process B 74/100 · Nearly there — weak spots: when it triggers

ProcedureAI and agentsData and analyticsSoftware 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
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
B
74/100
Nearly there
When it triggers w 12
20
Tools and files w 18
60
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: 2. 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 74/100

    • 20When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 10 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 660 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress
    • low The skill ranks results itself: that belongs to the system behind the tool, not the model

    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)
    • +4No input/output examples
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +3Description length 334: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 10 items
    • +3Output format is stated explicitly

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