SkillAgentSearch skills...

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-replay

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

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.

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

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.

SkillScoreStarsUpdatedFormat
transcript-replay (this skill)by hoangsonww811.0k10d agoSKILL.md
algorithmic-artby anthropics100177.9k11d agoSKILL.md
pptxby anthropics100177.9k11d agoSKILL.md
designby nextlevelbuilder100130.2k12d agoSKILL.md
ui-ux-pro-maxby nextlevelbuilder100130.2k12d agoSKILL.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.

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.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryOperations
Updated10d 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