[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BFBP30HDD93PBP3V19WAP":3,"skill-same:01M75BFBP30HDD93PBP3V19WAP":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75BFBP30HDD93PBP3V19WAP","agent-introspection-debugging",null,"Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fagent-introspection-debugging\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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":23,"description":7},"ECC","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fagent-introspection-debugging",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill agent-introspection-debugging",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill agent-introspection-debugging",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill agent-introspection-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fagent-introspection-debugging\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]