Agent Introspection Debugging
A structured capture, diagnose, recover loop for failing agent runs instead of blind retries.
- What
- A structured capture, diagnose, recover loop for failing agent runs instead of blind retries.
- Cost
- Free
- Needs
- the Muse app (mobile or web). Pure guidance skill, nothing to install. Most useful when an agent run is failing or looping.
- Level
- Beginner — the Muse app (mobile or web).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a structured self-debugging workflow for AI agent failures, built for the moment an agent run fails repeatedly, burns tokens without progress, loops on the same tools, or drifts away from its task. Instead of retrying blindly, the skill teaches a four-phase loop: capture the failure precisely (error, last meaningful tool sequence, what the agent was trying to do, context pressure, environment assumptions) with a minimum capture template, diagnose the common agent-specific failure patterns, apply contained recovery actions, and produce a structured human-readable introspection report. It sets scope boundaries too: use it for failure capture and diagnosis, not as a substitute for feature verification after code changes or for framework-specific debugging when a narrower skill exists. A workflow skill, not a hidden runtime: nothing executes automatically, the agent learns to debug itself before escalating to a human. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: written for coding-agent harnesses (Claude Code style runs with tool loops); in Muse it works as a diagnostic interview and method rather than automated capture, since Muse does not expose raw tool-call traces. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Agent Introspection Debugging is a free Muse skill that gives failing agent runs a structured capture, diagnose and recover loop instead of blind retries, so you find what actually broke, fix that cause, and get the run moving again, rather than rerunning the same failing steps and hoping for a different result.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Agent Introspection Debugging" with your Muse. Prerequisites: the Muse app (mobile or web). Pure guidance skill, nothing to install. Most useful when an agent run is failing or looping. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/agent-introspection-debugging/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "An agent run keeps failing: [describe what it was doing, the error, and the repeated pattern]. Run the introspection loop: capture, diagnose, recover." 3. Ask Muse to fill the failure capture template first (goal, error, last successful step, repeated pattern, environment assumptions), then diagnose before proposing any recovery action. Tip: the capture phase is the whole skill. A precise capture ("looping on file reads in /src/auth, 3rd retry, same 404") beats ten blind retries. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.