agent-introspection-debugging

Diagnose AI agent failures with a four-phase capture, diagnosis, recovery, and introspection workflow.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill agent-introspection-debugging-khunglong-03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-introspection-debugging
Source: https://github.com/khunglong-03/Pathora_Version3/tree/main/.cursor/skills/agent-introspection-debugging
Command: npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill agent-introspection-debugging-khunglong-03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.

Core Features & Use Cases

  • Phase-driven failure analysis: capture, diagnose, contained recovery, and introspection reporting.
  • Applies to failing agent runs that loop on tools, exhaust tokens, or drift from objectives.
  • Produces a structured debug report suitable for human review or automated escalation.

Quick Start

Run the agent introspection workflow on a failing session to produce a structured self-debug report.

Frequently Asked Questions about agent-introspection-debugging

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

FAQPage Schema
How do I debug an AI agent stuck in a repeated tool call loop?

Debug an AI agent stuck in a repeated tool call loop by capturing failures, context, and tool sequences to enable systematic root-cause diagnosis. This approach guides resolution within a contained recovery loop to stop non-progressing retries and resolve the workflow.

What is agent introspection for failure analysis?

Agent introspection for failure analysis is a structured workflow that diagnoses AI agent failures through four phases: failure capture, root-cause diagnosis, contained recovery, and an introspection report. It systematically identifies why an agent drifts from objectives or exhausts tokens.

How do I find the root cause of prompt drift in agent workflows?

Find the root cause of prompt drift in agent workflows by applying a phase-driven failure analysis. Capture the failing session context and tool sequences to diagnose the underlying issue and produce a structured debug report suitable for human review or automated escalation.

Does this debugging workflow require external dependencies or components?

This debugging workflow does not require external dependencies or components. It operates as a standalone phase-driven process using structured templates and guidance for escalation to diagnose failing agent runs that exhaust tokens or drift from objectives.

What's the best way to recover an agent from a non-progressing retry state?

The best way to recover an agent from a non-progressing retry state is using a contained recovery loop. This phase-driven approach captures the failure context and generates an introspection report to guide structured resolution without uncontrolled escalation.

When should I generate an introspection report for an agent failure?

Generate an introspection report for an agent failure when workflows exhibit repeated tool calls, exhaust tokens, or drift from objectives. The report provides structured debug output suitable for human review or automated escalation after root-cause diagnosis.