agentsclimarketplace

Session debug

Skill hoangsonww/Claude-Code-Agent-Monitor/plugins/ccam-devtools/skills/session-debug

πŸš€ A real-time monitoring dashboard for Claude Code, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, and WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics, a Kanban status board, status notifications, a cute buddy, and an interactive web UI/MacOS/Windows native app.

Install
npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-debug

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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).

SKILL.md

2.8 KB, as published. Nobody here has run it

Session Debug

Debug and inspect a Claude Code session from Agent Monitor data.

Input

The user provides: $ARGUMENTS

This may be:

  • A session ID to debug
  • "latest" or "last" for the most recent session
  • "errors" to find and debug the most recent errored session

Procedure

  1. Identify the target session:

    • If session ID given: GET /api/sessions/{id} from http://localhost:4820
    • If "latest": GET /api/sessions?limit=1 (default sort: most recently updated first)
    • If "errors": GET /api/sessions?limit=10&status=error
  2. Collect full session data:

    • Session metadata: status, model, cwd, timestamps, duration
    • Events: GET /api/events?session_id={session_id} β€” full event timeline
    • Agents: GET /api/agents?session_id={session_id} β€” all agents in session
    • Cost: GET /api/pricing/cost/{session_id}
  3. Analyze the session:

    Session Lifecycle

    • Start time β†’ first event β†’ last event β†’ end time
    • Status transitions (active β†’ working β†’ completed/error)
    • Total duration and active-vs-idle time

    Event Chain Analysis

    • Chronological event list with timestamps and durations
    • Identify the critical path (longest chain of dependent events)
    • Flag events that took unusually long
    • Highlight error events with full error context

    Agent Inspection

    • List all agents: type, task, status, duration
    • Subagent tree visualization (parent β†’ children)
    • Agents that failed and their last known state
    • Agent switching patterns (when and why new agents spawned)

    Tool Execution Trace

    • Every tool invocation in order with: tool name, duration, success/failure
    • Failed tool calls with error messages
    • Tool retry patterns (same tool called multiple times)

    Anomaly Detection

    • Events out of expected order
    • Gaps in event timeline (>30s with no events)
    • Duplicate events or agent states
    • Token usage spikes (compaction indicators)
  4. Diagnosis:

    • Root cause hypothesis (if errors present)
    • Contributing factors
    • Remediation suggestions

Output Format

Present as a debug report with:

  • Session summary header (ID, status, model, duration, cost)
  • Color-coded timeline (βœ… success, ❌ error, ⚠️ warning, ℹ️ info)
  • Agent tree diagram
  • Diagnosis section with numbered findings

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.