transcript-replay
/transcript-replay
Walk a Claude Code session transcript turn-by-turn from Agent Monitor data, summarizing each user, assistant, and tool message in order so a long conversation can be reviewed quickly. Anchors the recap to the session header (model, cost, turn_count). Use when reviewing what was actually said and done in a conversation.
- Author
- hoangsonww ↗
- Repository
- Claude-Code-Agent-Monitor ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Walk a Claude Code session transcript turn-by-turn from Agent Monitor data, summarizing each user, assistant, and tool message in order so a long conversation can be reviewed quickly. Anchors the recap to the session header (model, cost, turn_count). Use when reviewing what was actually said and done in a conversation.
Original author description
Walk a Claude Code session transcript turn-by-turn from Agent Monitor data, summarizing each user, assistant, and tool message in order so a long conversation can be reviewed quickly. Anchors the recap to the session header (model, cost, turn_count). Use when reviewing what was actually said and done in a conversation.
How it works
- Input
- Data Sources
- Report Sections
- Output
SKILL.md preview
--- name: transcript-replay description: > Walk a Claude Code session transcript turn-by-turn from Agent Monitor data, summarizing each user, assistant, and tool message in order so a long conversation can be reviewed quickly. Anchors the recap to the session header (model, cost, turn_count). Use when reviewing what was actually said and done in a conversation. --- # Transcript Replay Replay a session transcript one turn at a time with a concise summary of each message. ## Input The user provides: **$ARGUMENTS** - A **session ID** to replay, or - "latest" / "last" for the most recent session. - Optionally a turn range (e.g. `1-10`) or `errors` to focus on tool failures. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/sessions/:id/transcript` | ordered transcript messages: role (user / assistant / tool), content, tool_name and tool result where applicable, timestamps | | `GET /api/sessions/:id` | session header: status, model, cwd, started_at, ended_at, cost, metadata (thinking_blocks, turn_count, total_turn_duration_ms) | ## Report Sections ### 1. Header `GET /api/sessions/:id`. Print id, model, cwd basename, status, turn_count, thinking_blocks, total_turn_duration_ms, and cost in one block. ### 2. Turn-by-turn walk `GET /api/sessions/:id/transcript`. Iterate messages in order. For each turn emit one compact entry: - **user** — the request in one sentence (quote the literal ask only if short). - **assistant** — the decision / action taken, plus which tools it invoked. - **tool** — the tool name and a one-line result (success value or the error text); do not paste large tool payloads. Group an assistant message with the tool calls it triggered so each "turn" reads as intent → action → result. ### 3. Thread highlights After the walk, pull out: the original goal, the key turning points, any tool failures or retries, and how the session ended (resolved / errored / abandoned). ## Output A numbered turn list (`Turn N — <role>: <one-line summary>`), grouped intent → action → result, preceded by the header block and followed by the highlights. Truncate any quoted content past ~200 chars with `…`. Currency as USD to 4 decimal places. Summarize faithfully — never invent message content that is not in the transcript. If the transcript endpoint returns empty, say the session has no stored transcript (it may predate transcript capture or need a reimport) rather than fabricating turns. If the dashboard is unreachable, tell the user to start it with `npm start` from the repo root.
Files in this package (2)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named transcript-replay.
Database snapshot: 13.11.2026 · package version 89f5669fde95 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100transcript-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… - 90share-transcript:share
This skill should be used when the user asks to "share a transcript", "export a session", "convert a transcript", "share this conversation", "create a shareable transcript", "export to HTML", "export to markdown", or mentions sharing Claude Code sessions with others. - 100cwd-rollup
Roll up Claude Code sessions by working directory (project) from Agent Monitor data — session count, total cost, total tokens, and last-active timestamp per cwd — so per-project activity can be compared at a glance. Use when summarizing where effort and spend went across projects. - 100session-replay
Generate a self-contained HTML replay viewer of this project's Claude Code sessions. Use when the user wants to review, replay, or share what happened in past Claude Code sessions (prompts, tool calls, thinking, results) as an animated timeline. - 100share
Share a Claude Code session to pastila.nl and return a viewer link. Shares the current session by default, or a session specified as a transcript path, a session id, or a project. Use when the user asks to share, publish, or get a link to this conversation or to a session/transcript. - 100session-replay
Converts a Claude Code session JSONL file into an animated GIF terminal replay. Use when creating demos or visual evidence from past sessions.