agent-introspection-debugging

Guide AI agents through structured self-debugging and generate recovery reports.

2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill agent-introspection-debugging-momodaviluke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-introspection-debugging
Source: https://github.com/MomoDaviluke/star-citizen-promotion/tree/main/.agents/skills/ecc/agent-introspection-debugging
Command: npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill agent-introspection-debugging-momodaviluke

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve?

This workflow provides a structured, self-diagnostic loop for AI agents to catch, diagnose, and containedly recover from failures, reducing downtime and human escalation.

## Core Features & Use Cases

  • Four-Phase Loop: Failure Capture, Root-Cause Diagnosis, Contained Recovery, and Introspection Report.
  • Evidence-driven debugging templates to summarize failures, environment state, and tool usage.
  • Safe containment strategies that minimize side effects while restoring progress.
  • ECC integration prompts to align with verification-loop and continuous-learning workflows.

### Quick Start

Capture the failure, 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 debug AI agent failures during autonomous workflows?

To debug AI agent failures, use a structured self-diagnostic loop that captures failure evidence, diagnoses root causes, applies contained recovery, and generates an introspection report to restore progress safely.

What is structured introspection for autonomous agent context drift?

Structured introspection is a four-phase self-debugging workflow that captures evidence of context drift, diagnoses root causes, and applies contained recovery to minimize side effects while restoring progress.

How to recover from repeated failures and looping tool usage in AI agents?

Recover from looping tool usage by applying contained recovery strategies that minimize side effects, using evidence-driven templates to summarize failures and restore autonomous task progress safely.

Can I use this self-debugging workflow for ECC scenario continuous learning?

Yes, this self-debugging workflow includes ECC integration prompts that align introspection reports with verification-loop and continuous-learning workflows to reduce downtime and human escalation.

What is the best way to capture root-cause evidence when an agent run fails?

The best way to capture root-cause evidence is using structured debugging templates that summarize failures, environment state, and tool usage to produce a human-readable debug report.

When should I not use contained recovery for AI agent debugging?

You should avoid contained recovery when failures require immediate human escalation, although this workflow minimizes downtime by capturing evidence and diagnosing root causes before applying recovery strategies.