Help us improve
Share bugs, ideas, or general feedback.
From cc-telemetry
Use when the user reports a problem with a specific Claude Code session, needs to diagnose why something went wrong, wants to understand errors in detail, or asks "what happened in my last session". Trigger on phrases like "debug my session", "why did that fail", "what went wrong", "replay my session", or when investigating specific errors.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cc-telemetry:session-debuggingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help diagnose issues in specific Claude Code sessions by analyzing the complete session context including tool calls, errors, thinking blocks, and system messages.
Share bugs, ideas, or general feedback.
Help diagnose issues in specific Claude Code sessions by analyzing the complete session context including tool calls, errors, thinking blocks, and system messages.
Activate when the user:
If user doesn't specify which session:
/cc-telemetry:sessions to show recent sessionsGather comprehensive data:
/cc-telemetry:replay <session-id>
/cc-telemetry:errors --session <session-id>
/cc-telemetry:performance --session <session-id>
Look for:
For each error found:
Common root causes:
Present findings:
## Session Diagnosis: <session-slug>
**Summary**: [1-2 sentence description of what went wrong]
**Timeline**:
1. [timestamp] Claude thought: [thinking summary]
2. [timestamp] Tool called: [tool name with input]
3. [timestamp] ERROR: [error message]
**Root Cause**: [explanation of why it failed]
**Context**: [what led to this situation]
**Fix**: [how to avoid this in future]
User: "My last session kept failing on file writes"
/cc-telemetry:sessions --tail 1/cc-telemetry:replay <id>/cc-telemetry:search-errors "Write"/readonly/file.txt - the file is in a read-only directory"~/project/file.txt"User: "Why was my session so slow?"
/cc-telemetry:performance --session <id>Read tool took 15s because you were reading a 50MB log file"head or tail to read only relevant portions of large files"Use the telemetry-analyzer agent when:
npx claudepluginhub layerdynamics/lore --plugin cc-telemetryGenerates an in-chat session report from the active or named transcript — every tool call, sub-agent delegation, and file edit, with diagnostics for missed parallelism, redundant work, and over-serialization.
Analyzes Claude Code session logs to extract tool usage stats, thinking blocks, error patterns, debug trajectories, and generate actionable productivity recommendations. Provides cc-session CLI for overviews, timelines, searches.
Searches, recovers, and analyzes AI session histories across Claude Code, AI Studio, and Gemini CLI. Useful for recovering lost files after compaction, searching conversations, detecting corrections, and self-improvement workflows.