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)
Install / Use
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill transcript-replayInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Our assessment of transcript-replay
transcript-replay scores 81/100 on our quality scale, 628th of 751 Operations skills we index.
Its SKILL.md is 2.5 KB long, well organised into 8 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.
Maintenance, license and trust
- The repository was last updated 10 days ago, so transcript-replay is actively maintained.
- 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.
transcript-replay compared with similar skills
All 4 of these similar skills score higher than transcript-replay; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| transcript-replay (this skill)by hoangsonww | 81 | 1.0k | 10d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 11d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 11d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 130.2k | 12d ago | SKILL.md |
| ui-ux-pro-maxby nextlevelbuilder | 100 | 130.2k | 12d ago | SKILL.md |
Frequently asked questions
- How do I install transcript-replay?
- Run
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill transcript-replay. The install tabs above show the steps for each supported agent. - Which AI agents does transcript-replay 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 transcript-replay safe to use?
- 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 transcript-replay still maintained?
- The repository was last updated 10 days ago, so transcript-replay is actively maintained.
Skill content
View source on GitHubname: 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) orerrorsto 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.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
130.2kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
ui-ux-pro-max
130.2kUI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
