agent-introspection-debugging

Capture failure state, diagnose root causes, and generate introspection reports for AI agent runs.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/hbvg234/jnmt.vn --skill agent-introspection-debugging-hbvg234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-introspection-debugging
Source: https://github.com/hbvg234/jnmt.vn/tree/main/.claude/skills/agent-introspection-debugging
Command: npx skills add https://github.com/hbvg234/jnmt.vn --skill agent-introspection-debugging-hbvg234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and analyzes AI agent failures to prevent token waste and looping, by guiding systematic self-diagnosis and contained recovery.

Core Features & Use Cases

  • Failure capture: records error details, context, and recent tool calls.
  • Root-cause diagnosis: maps failures to known patterns and surfaces actionable hypotheses.
  • Contained recovery: applies small, reversible actions to regain progress and avoid escalation.
  • Introspection reporting: produces a structured report for humans or future agents.

Quick Start

Capture the current failure, run a root-cause diagnostic, apply 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 debug an AI agent that repeatedly fails or loops on tools?

Debug an AI agent that repeatedly fails by capturing the failure state, diagnosing root causes, and applying contained recovery. This structured self-debugging prevents token waste and stops tool looping before escalation.

What is structured self-debugging for AI agent failures?

Structured self-debugging is a four-phase workflow for AI agent failures: Failure Capture, Root-Cause Diagnosis, Contained Recovery, and Introspection Report. It records evidence and ensures traceability for humans or future agents.

How do I diagnose root causes when an AI agent drifts from task objectives?

Diagnose root causes for an agent drifting from task objectives by capturing the failure state, mapping errors to known patterns, and surfacing actionable hypotheses. This structured diagnosis guides subsequent contained recovery actions.

What is the best way to recover a failing AI agent without escalating the issue?

Recover a failing AI agent without escalation by applying contained recovery, which uses small, reversible actions to regain progress. This approach safely addresses the diagnosed root causes while preventing further token waste.

When do I need to generate an introspection report for AI agent failures?

Generate an introspection report for AI agent failures after completing failure capture, root-cause diagnosis, and contained recovery. It produces a structured record of evidence and traceability for humans or future agents.

Does structured agent debugging require any external dependencies or components?

Structured agent debugging requires no external dependencies or components to operate. It relies entirely on a four-phase workflow using a structured recovery checklist and templates to record evidence and ensure traceability.