[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7864FQ8NABWM71285DZWHBF":3,"skill-same:01M7864FQ8NABWM71285DZWHBF":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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7864FQ8NABWM71285DZWHBF","agent-introspection-debugging",null,"Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.","chenziyang110\u002Flaunchdeck","chenziyang110","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43693913?v=4","01M7863EBWK1D0P6A29YGEMAS4","Robin11","01M7863ECM1VB6RXDMHTW90D2T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fagent-introspection-debugging\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"agent-introspection-debugging\"\ndescription: \"Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.\"\ncompatibility: \"Requires spec-kit project structure with .specify\u002F directory\"\nmetadata:\n  author: \"github-spec-kit\"\n  source: \"templates\u002Fpassive-skills\u002Fagent-introspection-debugging\u002FSKILL.md\"\n---\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,"metadata":24,"description":7,"compatibility":27},{"author":25,"source":26},"github-spec-kit","templates\u002Fpassive-skills\u002Fagent-introspection-debugging\u002FSKILL.md","Requires spec-kit project structure with .specify\u002F directory","main","021f5cbe02157229460a577e9a585f2da6d78cb0",".claude\u002Fskills\u002Fagent-introspection-debugging","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck","https:\u002F\u002Fgithub.com\u002Fchenziyang110","2026-08-07 18:10:54",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add chenziyang110\u002Flaunchdeck --skill agent-introspection-debugging",{"tool":40,"command":41},"bunx","bunx skills add chenziyang110\u002Flaunchdeck --skill agent-introspection-debugging",{"tool":43,"command":44},"pnpm","pnpm dlx skills add chenziyang110\u002Flaunchdeck --skill agent-introspection-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fagent-introspection-debugging\u002FSKILL.md",true,[],[49,56,62,68,75,84],{"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":19},"01M7875F3HQ1GF5F6BR36KY3JE","launchdeck-agent","Codex host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fcodex\u002Fskill\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":58,"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":19},"01M7875DV2DQR33K1NFJHKAMZP","Claude host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fclaude\u002Fskill\u002FSKILL.md",[],[],{"skillNo":63,"name":51,"nameZh":6,"description":64,"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":19},"01M78759JQ7A6FQ8KDQTNYS3X9","Use this skill aggressively for local project lifecycle operations even when the user does not mention Launchdeck: start this project, run the dev server, dev, build, test, restart service, stop service, show logs, inspect ports, port is occupied, clean cache; and when the user explicitly asks to configure this local project for Launchdeck or create or generate a project-adapted `.launchdeck.yml`, including 为这个项目生成 Launchdeck 配置. Do not use for ordinary code edits, docs-only work, general explanations, API design discussion, or production deployment unless the user also asks to operate or configure a local project or service.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Fagent\u002Finstaller-payload\u002Fskill\u002Flaunchdeck-agent\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":19},"01M78753ZJQ7G2CZT1W1G8WRJV","zig-testing","Use ONLY when user explicitly requests Zig test code, built-in test runner configuration,\ntest failure diagnosis, or coverage for Zig projects.\n\nTriggers: \"write test zig\", \"zig test\", \"testing.allocator\", \"zig coverage\",\n\"comptime test\", \"zig expectError\", \"zig snapshot test\", \"zig fuzz\".\n\nDo NOT activate for: general Zig coding without test context, build.zig configuration\nfor non-test targets, Zig compiler errors, or Zig build system setup.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fzig-testing\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":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M78750JXY4Z5D5W1EX3PQ31Z","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7874X2T83EQQFRCEY5SJJVC","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fverification-before-completion\u002FSKILL.md",[],[]]