SkillAgentSearch skills...

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

Install / Use

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-timeline

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Category

Operations

Supported Platforms

Claude Code

Tags

Our assessment of session-timeline

session-timeline scores 81/100 on our quality scale, 665th of 753 Operations skills we index.

Its SKILL.md is 2.6 KB long, well organised into 10 sections and no code examples: a solid amount of guidance for an agent.

With 1,015 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so session-timeline is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

session-timeline compared with similar skills

All 4 of these similar skills score higher than session-timeline; compare them before choosing.

SkillScoreStarsUpdatedFormat
session-timeline (this skill)by hoangsonww811.0k55d agoSKILL.md
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md
prospectingby coreyhaines3110060.1k6d agoSKILL.md

Frequently asked questions

How do I install session-timeline?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-timeline. The install tabs above show the steps for each supported agent.
Which AI agents does session-timeline work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is session-timeline safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is session-timeline still maintained?
The repository was last updated about 2 months ago, so session-timeline is actively maintained.

name: session-timeline description: > 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.

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. Compute durations

Pair each PreToolUse with its matching PostToolUse (same tool_name, next occurrence) and show the tool's wall-clock duration. For TurnDuration events use the recorded duration directly. Flag any PreToolUse with no matching PostToolUse as unclosed.

4. Annotate notable points

Mark APIError (❌), Compaction (⚠️ context compressed), SubagentStop (subagent finished), Notification (ℹ️), and any timeline gap > 30s between consecutive events as an idle window.

5. Tallies

Event count by type, total tool time vs. session wall time, and the longest single tool call.

Output

A Markdown table — offset | event_type | tool_name | duration | summary — in strict timestamp order, preceded by the header line and followed by the tallies. Durations in ms or mm:ss.mmm; currency as USD to 4 decimal places. Never invent a duration when a PostToolUse is missing — label it unclosed. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryOperations
Updated1mo ago
Forks238

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions