skills.rest
LayerDynamics
LayerDynamicsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

session-debugging

Diagnose Claude Code session failures by analyzing tool calls and errors.

Updated Feb 25, 2026
Search Tags:#debugging#troubleshooting#claude code#telemetry#session analysis#error diagnosis
One-click install
npx skills add https://github.com/LayerDynamics/Lore --skill session-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-debugging
Source: https://github.com/LayerDynamics/Lore/tree/main/lore/extensions/cc-telemetry/skills/session-debugging
Command: npx skills add https://github.com/LayerDynamics/Lore --skill session-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users pinpoint and understand the root causes of errors or unexpected behavior within specific Claude Code sessions, enabling faster resolution of technical problems.

Core Features & Use Cases

  • Session Analysis: Deeply inspect tool calls, errors, and thinking processes of past sessions.
  • Error Diagnosis: Identify specific error messages, their context, and preceding actions.
  • Use Case: When a user reports "My last session failed to save the output," this skill can replay the session, identify the exact file write error, and explain that it was due to a permissions issue in the target directory.

Quick Start

Use session-debugging to diagnose why my last session failed.

Frequently Asked Questions about session-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why my Claude Code session failed to save output?▼

Diagnosing Claude Code session failures involves analyzing tool calls, errors, and system messages to pinpoint root causes like file write permission issues. This tracing of the execution timeline identifies the exact error origin and preceding actions.

What is the best way to trace tool call errors in Claude Code?▼

Tracing tool call errors requires analyzing session telemetry data to identify specific error messages and their execution context. This process reveals the preceding actions that triggered the unexpected behavior within your specific session.

Do I need session telemetry data to troubleshoot unexpected Claude Code behavior?▼

Yes, troubleshooting unexpected behavior requires access to session telemetry data including errors and performance metrics. This detailed telemetry enables the root cause analysis of specific session issues.

How does session analysis help with debugging Claude Code execution timelines?▼

Session analysis helps debugging by deeply inspecting tool calls, errors, and thinking processes of past sessions to trace execution timelines. It explains the exact context of error origins and preceding actions to resolve technical problems faster.

Can I understand the root cause of a Claude Code error without manually reading all system messages?▼

Yes, you can understand root causes by analyzing system messages and errors to automatically identify specific error contexts and preceding actions. This reveals the underlying issue, such as a directory permissions failure, without manual review.

Related Skills

Explore More Software Engineering Skills→
knowz-ioknowz-io
1

knowzcode-telemetry

Correlate Sentry and App Insights telemetry to diagnose production errors.

Official
Intermediate
narrative-ionarrative-io

lint

Identify and fix linting errors in TypeScript/JavaScript projects with bun check.

Official
Advanced
kunwl123456kunwl123456
26

auto-troubleshooter

Analyze log files to diagnose system issues and document new problems.

Community
Intermediate
ppiankovppiankov

logtap

Captures, triages, and analyzes ephemeral Kubernetes logs in real-time via CLI and sidecar injection.

Community
Advanced