[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YAJVMC9018VQCNS6JTHZ2":3,"skill-same:01M72YAJVMC9018VQCNS6JTHZ2":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72YAJVMC9018VQCNS6JTHZ2","agent-introspection-debugging",null,"Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fskills\u002Fagent-introspection-debugging\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: agent-introspection-debugging\ndescription: Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.\norigin: ECC\n---\n\n# Agent Introspection Debugging\n\nUse this skill when an agent run is failing repeatedly, consuming tokens without progress, looping on the same tools, or drifting away from the intended task.\n\nThis is a workflow skill, not a hidden runtime. It teaches the agent to debug itself systematically before escalating to a human.\n\n## When to Activate\n\n- Maximum tool call \u002F loop-limit failures\n- Repeated retries with no forward progress\n- Context growth or prompt drift that starts degrading output quality\n- File-system or environment state mismatch between expectation and reality\n- Tool failures that are likely recoverable with diagnosis and a smaller corrective action\n\n## Scope Boundaries\n\nActivate this skill for:\n- capturing failure state before retrying blindly\n- diagnosing common agent-specific failure patterns\n- applying contained recovery actions\n- producing a structured human-readable debug report\n\nDo not use this skill as the primary source for:\n- feature verification after code changes; use `verification-loop`\n- framework-specific debugging when a narrower ECC skill already exists\n- runtime promises the current harness cannot enforce automatically\n\n## Four-Phase Loop\n\n### Phase 1: Failure Capture\n\nBefore trying to recover, record the failure precisely.\n\nCapture:\n- error type, message, and stack trace when available\n- last meaningful tool call sequence\n- what the agent was trying to do\n- current context pressure: repeated prompts, oversized pasted logs, duplicated plans, or runaway notes\n- current environment assumptions: cwd, branch, relevant service state, expected files\n\nMinimum capture template:\n\n```markdown\n## Failure Capture\n- Session \u002F task:\n- Goal in progress:\n- Error:\n- Last successful step:\n- Last failed tool \u002F command:\n- Repeated pattern seen:\n- Environment assumptions to verify:\n```\n\n### Phase 2: Root-Cause Diagnosis\n\nMatch the failure to a known pattern before changing anything.\n\n| Pattern | Likely Cause | Check |\n| --- | --- | --- |\n| Maximum tool calls \u002F repeated same command | loop or no-exit observer path | inspect the last N tool calls for repetition |\n| Context overflow \u002F degraded reasoning | unbounded notes, repeated plans, oversized logs | inspect recent context for duplication and low-signal bulk |\n| `ECONNREFUSED` \u002F timeout | service unavailable or wrong port | verify service health, URL, and port assumptions |\n| `429` \u002F quota exhaustion | retry storm or missing backoff | count repeated calls and inspect retry spacing |\n| file missing after write \u002F stale diff | race, wrong cwd, or branch drift | re-check path, cwd, git status, and actual file existence |\n| tests still failing after “fix” | wrong hypothesis | isolate the exact failing test and re-derive the bug |\n\nDiagnosis questions:\n- is this a logic failure, state failure, environment failure, or policy failure?\n- did the agent lose the real objective and start optimizing the wrong subtask?\n- is the failure deterministic or transient?\n- what is the smallest reversible action that would validate the diagnosis?\n\n### Phase 3: Contained Recovery\n\nRecover with the smallest action that changes the diagnosis surface.\n\nSafe recovery actions:\n- stop repeated retries and restate the hypothesis\n- trim low-signal context and keep only the active goal, blockers, and evidence\n- re-check the actual filesystem \u002F branch \u002F process state\n- narrow the task to one failing command, one file, or one test\n- switch from speculative reasoning to direct observation\n- escalate to a human when the failure is high-risk or externally blocked\n\nDo not claim unsupported auto-healing actions like “reset agent state” or “update harness config” unless you are actually doing them through real tools in the current environment.\n\nContained recovery checklist:\n\n```markdown\n## Recovery Action\n- Diagnosis chosen:\n- Smallest action taken:\n- Why this is safe:\n- What evidence would prove the fix worked:\n```\n\n### Phase 4: Introspection Report\n\nEnd with a report that makes the recovery legible to the next agent or human.\n\n```markdown\n## Agent Self-Debug Report\n- Session \u002F task:\n- Failure:\n- Root cause:\n- Recovery action:\n- Result: success | partial | blocked\n- Token \u002F time burn risk:\n- Follow-up needed:\n- Preventive change to encode later:\n```\n\n## Recovery Heuristics\n\nPrefer these interventions in order:\n\n1. Restate the real objective in one sentence.\n2. Verify the world state instead of trusting memory.\n3. Shrink the failing scope.\n4. Run one discriminating check.\n5. Only then retry.\n\nBad pattern:\n- retrying the same action three times with slightly different wording\n\nGood pattern:\n- capture failure\n- classify the pattern\n- run one direct check\n- change the plan only if the check supports it\n\n## Integration with ECC\n\n- Use `verification-loop` after recovery if code was changed.\n- Use `continuous-learning-v2` when the failure pattern is worth turning into an instinct or later skill.\n- Use `council` when the issue is not technical failure but decision ambiguity.\n- Use `workspace-surface-audit` if the failure came from conflicting local state or repo drift.\n\n## Output Standard\n\nWhen this skill is active, do not end with “I fixed it” alone.\n\nAlways provide:\n- the failure pattern\n- the root-cause hypothesis\n- the recovery action\n- the evidence that the situation is now better or still blocked\n","# Agent Introspection Debugging\n\nUse this skill when an agent run is failing repeatedly, consuming tokens without progress, looping on the same tools, or drifting away from the intended task.\n\nThis is a workflow skill, not a hidden runtime. It teaches the agent to debug itself systematically before escalating to a human.\n\n## When to Activate\n\n- Maximum tool call \u002F loop-limit failures\n- Repeated retries with no forward progress\n- Context growth or prompt drift that starts degrading output quality\n- File-system or environment state mismatch between expectation and reality\n- Tool failures that are likely recoverable with diagnosis and a smaller corrective action\n\n## Scope Boundaries\n\nActivate this skill for:\n- capturing failure state before retrying blindly\n- diagnosing common agent-specific failure patterns\n- applying contained recovery actions\n- producing a structured human-readable debug report\n\nDo not use this skill as the primary source for:\n- feature verification after code changes; use `verification-loop`\n- framework-specific debugging when a narrower ECC skill already exists\n- runtime promises the current harness cannot enforce automatically\n\n## Four-Phase Loop\n\n### Phase 1: Failure Capture\n\nBefore trying to recover, record the failure precisely.\n\nCapture:\n- error type, message, and stack trace when available\n- last meaningful tool call sequence\n- what the agent was trying to do\n- current context pressure: repeated prompts, oversized pasted logs, duplicated plans, or runaway notes\n- current environment assumptions: cwd, branch, relevant service state, expected files\n\nMinimum capture template:\n\n```markdown\n## Failure Capture\n- Session \u002F task:\n- Goal in progress:\n- Error:\n- Last successful step:\n- Last failed tool \u002F command:\n- Repeated pattern seen:\n- Environment assumptions to verify:\n```\n\n### Phase 2: Root-Cause Diagnosis\n\nMatch the failure to a known pattern before changing anything.\n\n| Pattern | Likely Cause | Check |\n| --- | --- | --- |\n| Maximum tool calls \u002F repeated same command | loop or no-exit observer path | inspect the last N tool calls for repetition |\n| Context overflow \u002F degraded reasoning | unbounded notes, repeated plans, oversized logs | inspect recent context for duplication and low-signal bulk |\n| `ECONNREFUSED` \u002F timeout | service unavailable or wrong port | verify service health, URL, and port assumptions |\n| `429` \u002F quota exhaustion | retry storm or missing backoff | count repeated calls and inspect retry spacing |\n| file missing after write \u002F stale diff | race, wrong cwd, or branch drift | re-check path, cwd, git status, and actual file existence |\n| tests still failing after “fix” | wrong hypothesis | isolate the exact failing test and re-derive the bug |\n\nDiagnosis questions:\n- is this a logic failure, state failure, environment failure, or policy failure?\n- did the agent lose the real objective and start optimizing the wrong subtask?\n- is the failure deterministic or transient?\n- what is the smallest reversible action that would validate the diagnosis?\n\n### Phase 3: Contained Recovery\n\nRecover with the smallest action that changes the diagnosis surface.\n\nSafe recovery actions:\n- stop repeated retries and restate the hypothesis\n- trim low-signal context and keep only the active goal, blockers, and evidence\n- re-check the actual filesystem \u002F branch \u002F process state\n- narrow the task to one failing command, one file, or one test\n- switch from speculative reasoning to direct observation\n- escalate to a human when the failure is high-risk or externally blocked\n\nDo not claim unsupported auto-healing actions like “reset agent state” or “update harness config” unless you are actually doing them through real tools in the current environment.\n\nContained recovery checklist:\n\n```markdown\n## Recovery Action\n- Diagnosis chosen:\n- Smallest action taken:\n- Why this is safe:\n- What evidence would prove the fix worked:\n```\n\n### Phase 4: Introspection Report\n\nEnd with a report that makes the recovery legible to the next agent or human.\n\n```markdown\n## Agent Self-Debug Report\n- Session \u002F task:\n- Failure:\n- Root cause:\n- Recovery action:\n- Result: success | partial | blocked\n- Token \u002F time burn risk:\n- Follow-up needed:\n- Preventive change to encode later:\n```\n\n## Recovery Heuristics\n\nPrefer these interventions in order:\n\n1. Restate the real objective in one sentence.\n2. Verify the world state instead of trusting memory.\n3. Shrink the failing scope.\n4. Run one discriminating check.\n5. Only then retry.\n\nBad pattern:\n- retrying the same action three times with slightly different wording\n\nGood pattern:\n- capture failure\n- classify the pattern\n- run one direct check\n- change the plan only if the check supports it\n\n## Integration with ECC\n\n- Use `verification-loop` after recovery if code was changed.\n- Use `continuous-learning-v2` when the failure pattern is worth turning into an instinct or later skill.\n- Use `council` when the issue is not technical failure but decision ambiguity.\n- Use `workspace-surface-audit` if the failure came from conflicting local state or repo drift.\n\n## Output Standard\n\nWhen this skill is active, do not end with “I fixed it” alone.\n\nAlways provide:\n- the failure pattern\n- the root-cause hypothesis\n- the recovery action\n- the evidence that the situation is now better or still blocked\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","everything-claude-code\u002Fskills\u002Fagent-introspection-debugging",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill agent-introspection-debugging",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill agent-introspection-debugging",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill agent-introspection-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fskills\u002Fagent-introspection-debugging\u002FSKILL.md",true,[],[49,57,62,68,75,82],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":58,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":56},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":56},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":56},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":56},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":56},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]