Agent skill · Data & Analytics

session-timeline

Render an ordered timeline of one Claude Code session's events (every event type) with per-event durations and tool names, reconstructed from Agent Monitor data. Pairs PreToolUse with PostToolUse to compute tool durations and surfaces gaps, errors, and compaction points. Use when reconstructing what happened in a session step by step.

hoangsonww869★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-timeline --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Path: plugins/ccam-sessions/skills/session-timeline/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 869
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Session Timeline Reconstruct the chronological event timeline of a single Claude Code session. ## Input The user provides: **$ARGUMENTS** - A **session ID** to time-line, or - "latest" / "last" for the most recent session. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/sessions/:id` | session header: status, model, cwd, started_at, ended_at, cost, metadata (thinking_blocks, turn_count, total_turn_duration_ms) — and nested events | | `GET /api/events?session_id=X` | the full event stream: event_type (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, Notification, Compaction, APIError, TurnDuration), tool_name, summary, data, timestamp | ## Report Sections ### 1. Resolve & header If "latest", `GET /api/sessions?limit=1` to get the id, then `GET /api/sessions/:id`. Print a one-line header: id, status, model, cwd basename, started_at → ended_at, turn_count, total_turn_duration_ms, cost. ### 2. Build the ordered timeline `GET /api/events?session_id=X`. Sort strictly by `timestamp`. For each event emit a row with: relative offset from `started_at` (e.g. `+00:03.412`), event_type, tool_name (when present), and a one-line `summary`. ### 3.

What's inside
Steps it walks through
  1. Input
  2. Data Sources
  3. Report Sections
  4. 1. Resolve & header
  5. 2. Build the ordered timeline
  6. 3. Compute durations
  7. 4. Annotate notable points
  8. 5. Tallies
  9. Output
More from Claude-Code-Agent-Monitor
All skills →
About this skill
What does the session-timeline skill do?

Render an ordered timeline of one Claude Code session's events (every event type) with per-event durations and tool names, reconstructed from Agent Monitor data. Pairs PreToolUse with PostToolUse to compute tool durations and surfaces gaps, errors, and compaction points. Use when reconstructing what happened in a session step by step.

How do I install it?

Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-timeline --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.

Keep going