agent-trace-analyzer

Analyze Claude Code agent session logs to explain decisions and identify failure root causes.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/saddam-eng-tech/ai-agent-skills --skill agent-trace-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-trace-analyzer
Source: https://github.com/saddam-eng-tech/ai-agent-skills/tree/main/agent-trace-analyzer
Command: npx skills add https://github.com/saddam-eng-tech/ai-agent-skills --skill agent-trace-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users understand why an AI agent made specific decisions, identify the root causes of errors or unexpected behavior, and receive actionable suggestions for improvement.

Core Features & Use Cases

  • Decision Analysis: Breaks down agent session logs to explain each decision made.
  • Root Cause Identification: Classifies issues like missing instructions, context rot, or incorrect tool usage.
  • Remediation Suggestions: Provides targeted fixes, including updates to CLAUDE.md or tool configurations.
  • Use Case: When an AI agent fails to complete a task correctly, use this Skill to analyze the session trace and pinpoint the exact reason for the failure, then get advice on how to prevent it next time.

Quick Start

Analyze the attached agent session log to understand why the agent failed.

Frequently Asked Questions about agent-trace-analyzer

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

FAQPage Schema
How do I debug AI agent decisions from session logs?

To debug AI agent decisions from session logs, analyze the traces to explain each decision point, identify root causes of failures like missing instructions or context rot, and receive actionable remediation suggestions.

Why does my AI agent fail to complete a task correctly?

Your AI agent fails correctly completing tasks due to root causes like missing instructions, context rot, wrong tool selection, or hallucinations, which are identified by analyzing agent session logs and decision points.

What is the best way to troubleshoot AI agent hallucinations and wrong tool selection?

The best way to troubleshoot AI agent hallucinations and wrong tool selection is to analyze the session trace to pinpoint the exact decision point causing the failure, then apply targeted fixes to tool configurations.

How do I fix context rot in AI agent session traces?

To fix context rot in AI agent session traces, analyze the logs to classify the issue at the decision point, then apply targeted remediation planning by updating instructions in your CLAUDE.md file.

Can I use session log analysis for remediation planning in CLAUDE.md?

Yes, you can use session log analysis for remediation planning in CLAUDE.md, as the process identifies missing instructions and provides targeted fixes to update your tool configurations and prevent future failures.

What are the limitations of troubleshooting agent failures using session logs?

Troubleshooting agent failures using session logs requires the analysis of complete decision points and traces, meaning limitations arise if session logs are incomplete or lack the context needed to identify the root cause.