event-trace
SolidTrace the full event chain for one Claude Code session into an ordered timeline of every event type with tool_name and summary, highlighting gaps, out-of-order events, and failures. Reads /api/events?session_id= and /api/sessions/:id from the Agent Monitor dashboard. Use when debugging what a session actually did, step by step.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- hoangsonww
- Repository
- hoangsonww/Claude-Code-Agent-Monitor
- Created
- 4 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
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).
transcript-grep
Search a Claude Code session transcript for a string or regex pattern and show every matching message with surrounding context. Reads /api/sessions/:id/transcript and resolves sessions via /api/sessions?limit= from the Agent Monitor dashboard. Use when hunting for a specific message, prompt, tool call, or error inside a session's conversation.
cctrace
Trace, inspect, and replay Claude Code's HTTP traffic with cctrace — a TLS-intercepting tracer with a live web UI. Use this skill whenever the user wants to see what Claude Code sends over the wire (system prompts, tools, token usage, cache hits, cost, usage limits, errors), debug a Claude Code session ("why did it do that", "what did the agent see", "why is my cache hit rate low", "how much did that session cost"), capture API traffic for a bug report, replay or share a captured session, work with saved .jsonl traces (view, clean, merge, compress), or find which port a running cctrace instance is on. Also use it when the user mentions cctrace, trace files in a .cctrace/ directory, MITM-capturing Claude traffic, tracing a third-party ANTHROPIC_BASE_URL provider, or tracing the codex / grok / kimi CLIs.