agent-introspection-debugging

Diagnoses failing agent runs through structured capture, root-cause analysis, and contained recovery.

Updated May 19, 2026
One-click install
npx skills add https://github.com/azusagasaku/--claude-config --skill agent-introspection-debugging-azusagasaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-introspection-debugging
Source: https://github.com/azusagasaku/--claude-config/tree/main/skills/ecc/agent-introspection-debugging
Command: npx skills add https://github.com/azusagasaku/--claude-config --skill agent-introspection-debugging-azusagasaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agent runs often fail by looping on the same tool calls, burning tokens without progress, or drifting from the intended task. This Skill provides a structured self-debugging workflow so the agent captures the failure, diagnoses the root cause, applies a minimal recovery, and reports the outcome instead of retrying blindly. ## Core Features & Use Cases - Four-Phase Debug Loop: Failure capture, root-cause diagnosis, contained recovery, and a structured introspection report. - Failure Pattern Table: Maps common symptoms like maximum tool calls, context overflow, ECONNREFUSED, 429 quota exhaustion, and stale file state to likely causes and checks. - Recovery Heuristics: Prioritizes restating the objective, verifying world state, shrinking scope, and running one discriminating check before retrying. - Use Case: When an agent hits a loop-limit failure after repeating the same command, use this Skill to record the failure state, classify the pattern, run one direct check, and produce a human-readable self-debug report. ## Quick Start Use the agent-introspection-debugging skill to diagnose why this agent run keeps looping on the same tool call and produce a recovery report.

Frequently Asked Questions about agent-introspection-debugging

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

FAQPage Schema
What causes an agent to burn tokens without making progress?▼

Common causes include unbounded notes, repeated plans, oversized pasted logs, and retry storms without backoff. The diagnosis phase classifies whether the failure is logic, state, environment, or policy related before any recovery action is taken.

When should I use agent self-debugging instead of verification-loop?▼

Use this workflow when a run is failing, looping, or drifting from its task. Use verification-loop afterward if code was changed during recovery, since this Skill is not intended for feature verification after code changes.

Can this workflow automatically reset agent state or harness config?▼

No. The Skill explicitly forbids claiming unsupported auto-healing actions like resetting agent state or updating harness config unless they are performed through real tools in the current environment. It is a workflow guide, not a hidden runtime.

Why does my agent keep failing after applying a fix?▼

Tests still failing after a fix usually indicates a wrong hypothesis. The recommended action is to isolate the exact failing test, re-derive the bug from direct observation, and shrink the scope to one failing command, file, or test.