agent-teams/skills/view-team-session/SKILL.md
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.
npx skillsauth add kenneth-liao/ai-launchpad-marketplace view-team-sessionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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.
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 browserThe script will:
~/.claude/projects/*/ to find the session's JSONL fileteamName field and enrich with team config from ~/.claude/teams/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.
The generated HTML is a single self-contained file with:
Output files go to .claude/output/ by default.
development
Manage scheduled Claude Code tasks — add (recurring or one-off), list, pause, resume, remove, view results, and test execution of skills, prompts, and scripts with safety controls and notifications. Use when the user mentions scheduling, cron, automated tasks, recurring tasks, background tasks, running something on a schedule, periodic execution, or wants a skill/prompt/script to run automatically at a set time. Cross-platform (macOS, Linux, Windows).
tools
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".
tools
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".
tools
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".