SKILLEMALL.ai
GitHub ↗ RU Sign in

CB session-debug

Debug a specific session by inspecting its full event chain (PreToolUse, PostToolUse, Stop, SubagentStop, Compaction, APIError, TurnDuration, Notification events), agent hierarchy (recursive parent/child tree with subagent_type and depth), token usage with compaction baselines, workflow intelligence data (orchestration DAG, error propagation by depth), and session metadata (thinking_blocks, turn_count, total_turn_duration_ms).

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

Debug a specific session by inspecting its full event chain (PreToolUse, PostToolUse, Stop, SubagentStop, Compaction, APIError, TurnDuration, Notification…

As a process B 75/100 · Nearly there — weak spots: when it triggers, progress reporting

ProcedureSoftware 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
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
B
75/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Failures and branches w 10
50
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 75/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 39 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 586 tokens
  • 100Running it twice. No mutating operations

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 430: enough signal without eating the budget
  • +4Structure: 4 headings
  • +3Step-by-step instructions: 39 items
  • +3Output format is stated explicitly

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