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).
Profile →npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-debug --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Input
- Procedure
- Output Format
What does the session-debug skill do?
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).
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-debug --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.