event-trace
Trace 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.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace --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.
# Event Trace Build a chronological, annotated event timeline for a single session. ## Input The user provides: **$ARGUMENTS** This is a session ID. It may also be: - `latest` / `last` — trace the most recently updated session - `errors` — trace the most recent session whose status is `error` ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/sessions?limit=N` | session list (used to resolve `latest`/`errors` and the target id) | | `GET /api/sessions/:id` | full session detail (status, model, cwd, started_at, ended_at, cost, nested agents + events) | | `GET /api/events?session_id=X` | the ordered event stream: event_type, tool_name, summary, data, timestamp | ## Report Sections ### 1. Resolve the session If `$ARGUMENTS` is a raw id, use it. If `latest`/`last`, call `GET /api/sessions?limit=1`. If `errors`, call `GET /api/sessions?limit=10&status=error` and pick the newest. Confirm the id resolves via `GET /api/sessions/:id`; if not, report it as missing and stop. ### 2. Session header From `GET /api/sessions/:id`: id, status, model, cwd, started_at → ended_at, total duration, cost (USD to 4 decimals), and counts (events, agents). ### 3. Ordered timeline From
- Input
- Data Sources
- Report Sections
- 1. Resolve the session
- 2. Session header
- 3. Ordered timeline
- 4. Gap & failure highlights
- 5. Verdict
- Output
What does the event-trace skill do?
Trace 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.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace --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.