Agent skill
view-team-session
Generate a self-contained HTML viewer for any Claude Code session, including agent team sessions with full inter-agent DM timelines. Use whenever the user asks to "view a session", "visualize a conversation", "show me what happened in session X", "generate a session viewer", "replay a session", "show me what my agents did", "session replay", "team timeline", or references viewing/inspecting Claude Code JSONL logs. Also use when the user provides a session ID and wants to see the conversation.
Install this agent skill to your Project
npx add-skill https://github.com/kenneth-liao/ai-launchpad-marketplace/tree/main/agent-teams/skills/view-team-session
SKILL.md
View Team Session
Generate a self-contained HTML viewer from Claude Code session JSONL logs. Works for both solo sessions and agent team sessions, showing the full conversation timeline with filtering, search, and collapsible tool calls.
How It Works
Claude Code stores conversation logs as JSONL files at
~/.claude/projects/<project>/<session-id>.jsonl. When agent teams are used,
each agent gets its own JSONL file in the same project directory, linked by a
shared teamName field. Team config is stored at ~/.claude/teams/{team-name}/config.json.
Browsers can't read local JSONL files directly, so the skill uses a Python script to extract the data and embed it into a self-contained HTML playground.
Usage
Run the generate script with a session ID using uv run:
uv run ${CLAUDE_SKILL_DIR}/scripts/generate.py SESSION_ID [--output path] [--no-open]
SESSION_ID— the UUID from the JSONL filename (e.g.,605eef0e-40be-4e0f-8a34-0a977c60399d)--output path— custom output path (default:.claude/output/<session-id>.html)--no-open— skip auto-opening in browser
The script will:
- Scan
~/.claude/projects/*/to find the session's JSONL file - If it's a team session, discover all teammate JSONL files via the shared
teamNamefield and enrich with team config from~/.claude/teams/ - Parse all files into structured events (speech, DMs, tool calls, task management, thinking, etc.)
- Deduplicate inter-agent DMs (each DM exists in both sender and receiver logs — only the sender's copy is kept since it has richer metadata)
- Embed the data into the HTML template and write the output file
Finding Session IDs
If the user doesn't provide a session ID, help them find one:
# List recent sessions for the current project
ls -lt ~/.claude/projects/<project>/*.jsonl | head -10
# Search for sessions containing specific content
grep -l "search term" ~/.claude/projects/<project>/*.jsonl
The session ID is the filename without the .jsonl extension.
Output
The generated HTML is a single self-contained file with:
- Header showing team name, session ID, duration, event count
- Sidebar with agent toggles, event type filters, and content search
- Timeline of event cards with agent-colored borders
- Task management events highlighted (task creation, assignment, completion, dependencies)
- Default view shows speech and DMs only; tool calls, thinking, and system events are togglable
- Dark theme (GitHub-dark style)
Output files go to .claude/output/ by default.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
test-skill
Run or generate test suites for any skill. Use when testing a skill before deployment, after making changes, before/after plugin upgrades, when validating skill behavior, or when the user says "test skill", "run skill tests", "generate tests for skill", or "check for regressions".
upgrade-plugin
Upgrade a plugin's skills, hooks, and patterns to align with latest Claude Code capabilities and best practices. Use when a plugin needs modernization, after Claude Code updates, or when the user says "upgrade plugin", "modernize plugin", or "update plugin to latest patterns".
skill-retro
Use when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review skills", "how did skills do", "improve this skill", or "skill retrospective".
analyze-team-session
Use when reviewing an agent team session export for quality, when asked to "analyze this team session", "review my agent team run", "what went wrong with this session", "how can I improve my agent team usage", or when provided a markdown team session transcript and asked for feedback on agent teams effectiveness.
youtube-data
Retrieve YouTube data using the YouTube Data API. Use when you need to search videos, get video or channel details, fetch transcripts, read comments, find trending or related content, or when the user mentions 'YouTube data', 'video stats', 'transcript', or 'channel info'.
write
Generalized writing skill that produces written content for any platform and format. Use when asked to write, draft, or create a newsletter, YouTube script, guide, sales page, Twitter thread, LinkedIn post, Substack Note, or community post. Also use when the user says "write this up", "draft a post", "create content about", or needs any written output.
Didn't find tool you were looking for?