agent-introspection-debugging

Diagnoses AI agent failures and applies contained recovery actions.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/GGEdu/claude-god-mode-template --skill agent-introspection-debugging-ggedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-introspection-debugging
Source: https://github.com/GGEdu/claude-god-mode-template/tree/main/skills/agent-introspection-debugging
Command: npx skills add https://github.com/GGEdu/claude-god-mode-template --skill agent-introspection-debugging-ggedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

This skill provides a disciplined, repeatable approach to diagnosing and recovering from stubborn agent failures, reducing token waste and drift by capturing failure state, pinpointing root causes, applying contained recovery actions, and producing structured introspection reports for humans.

Core Features & Use Cases

  • Failure capture: records error type, last successful step, environment details, and notable context to reproduce the issue.
  • Root-cause diagnosis: maps failures to known patterns, asks diagnostic questions, and suggests targeted remedies.
  • Contained recovery: executes the smallest safe action to restore progress without broad re-execution.
  • Introspection reporting: final report that summarizes failure, root cause, remediation, and follow-up steps.
  • ECC integration: works with verification loops and human-in-the-loop gates to ensure safe rollback.

Quick Start

Initiate a session with agent-introspection-debugging to capture a failure state, diagnose the root cause, apply a contained recovery, and generate an introspection 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 diagnose and recover from persistent AI agent failures?

Persistent AI agent failures are resolved by capturing the failure state, diagnosing root causes, and applying contained recovery actions. This structured debugging workflow reduces token waste and drift while producing an introspection report for humans.

What is contained recovery in agent debugging?

Contained recovery in agent debugging executes the smallest safe action to restore progress without broad re-execution. It integrates with verification loops and human-in-the-loop gates to ensure safe rollback before escalation.

Why does my AI agent get stuck in repeated tool-call loops and retries?

AI agents get stuck in repeated tool-call loops and retries due to prompt drift, environment mismatches, or persistent failures. Root-cause diagnosis maps these failures to known patterns, asks diagnostic questions, and suggests targeted remedies to resolve them.

Do I need a specific framework to use structured agent introspection reporting?

No specific framework dependency is required to use structured agent introspection reporting. It satisfies requirements for structured failure capture, root-cause analysis, and introspection reporting within ECC-based agent systems and works with verification loops.

What's the best way to capture failure state for reproducing AI agent errors?

The best way to capture failure state for reproducing AI agent errors is to record the error type, last successful step, environment details, and notable context. This structured failure capture enables accurate root-cause diagnosis and targeted remediation.