[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XC53R5MN96R0CZ9FH9TKV4":3,"skill-same:01M6XC53R5MN96R0CZ9FH9TKV4":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6XC53R5MN96R0CZ9FH9TKV4","zero-iteration-failure-analysis",null,"Identify and handle agent failures with 0 iterations as pre-execution system issues","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fzero-iteration-failure-analysis\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27],"ZeRO","analysis","iteration","failure analysis","zero iteration failure analysis","issues","execution","system","as","with","2026-11-10 10:12:30",false,"---\nname: zero-iteration-failure-analysis\ndescription: Identify and handle agent failures with 0 iterations as pre-execution system issues\n---\n\n# Zero-Iteration Failure Analysis\n\nThis skill provides a workflow for detecting and responding to agent failures that occur before any iterations are executed. These failures indicate system-level problems rather than task execution issues.\n\n## When to Apply\n\nUse this skill when analyzing agent execution results and you observe:\n- **0 iterations** reported in the execution summary\n- **No tool invocations** in the conversation log\n- **No artifacts created** (no files, outputs, or intermediate results)\n- **Error message** present but no agent reasoning visible\n\n## Identification Checklist\n\nA zero-iteration failure is confirmed when **ALL** of the following are true:\n\n```\n[ ] Iteration count = 0\n[ ] Tool usage count = 0  \n[ ] No conversation log beyond initial instruction\n[ ] Error\u002Fself-report indicates failure before execution began\n```\n\n## Failure Mode Classification\n\n| Indicator | Failure Type | Investigation Level |\n|-----------|--------------|---------------------|\n| 0 iterations, 0 tools | Pre-execution | System-level |\n| 1+ iterations, error mid-task | Execution | Agent-level |\n| 1+ iterations, wrong output | Reasoning | Agent-level |\n\n## Investigation Steps\n\n### Step 1: Confirm Zero-Iteration Status\n\n```python\ndef is_zero_iteration_failure(execution_result):\n    \"\"\"Check if failure occurred before any agent iterations.\"\"\"\n    return (\n        execution_result.get('iterations', 0) == 0 and\n        execution_result.get('tool_calls', []) == [] and\n        execution_result.get('artifacts', []) == []\n    )\n```\n\n### Step 2: Extract Error Context\n\nExamine any error message or self-report for clues:\n- **Initialization errors**: Environment setup, dependency missing, config invalid\n- **Prompt parsing errors**: Malformed instruction, missing required fields\n- **Resource errors**: Memory limits, timeout before start, permission denied\n\n### Step 3: Route to Appropriate Investigation\n\n```\nIF zero-iteration failure detected:\n    → Escalate to SYSTEM investigation\n    → Do NOT attempt agent-level debugging\n    → Check: environment, dependencies, prompt format, resource limits\nELSE:\n    → Proceed with standard agent failure analysis\n```\n\n### Step 4: Document the Failure Mode\n\nRecord the failure with appropriate categorization:\n\n```yaml\nfailure_analysis:\n  type: zero-iteration\n  severity: high\n  investigation_level: system\n  agent_debugging_appropriate: false\n  recommended_actions:\n    - Check execution environment health\n    - Verify prompt\u002Finput formatting\n    - Review system logs for initialization errors\n    - Validate resource availability\n```\n\n## Common Causes and Resolutions\n\n| Cause | Symptoms | Resolution |\n|-------|----------|------------|\n| Environment crash | Immediate error, no context | Restart environment, check dependencies |\n| Prompt parse failure | Error mentions instruction format | Validate input schema, fix formatting |\n| Resource exhaustion | Timeout or memory error before start | Increase limits, optimize initialization |\n| Permission denied | Access error on startup | Check file\u002Fsystem permissions |\n\n## Escalation Criteria\n\nImmediately flag for system-level review when:\n- Zero-iteration failures occur repeatedly (>2 in same session)\n- Error messages indicate infrastructure issues\n- Multiple agents fail with same zero-iteration pattern\n\n## Example Analysis\n\n```\nEXECUTION SUMMARY:\n- Iterations: 0\n- Tools Used: None\n- Artifacts: None\n- Status: Failed\n- Error: \"Agent initialization failed: missing required config\"\n\nANALYSIS:\n✓ Zero-iteration failure detected\n✓ Pre-execution failure mode confirmed\n→ Action: Escalate to system investigation\n→ Do NOT debug agent reasoning (no reasoning occurred)\n→ Check: config loading, environment variables, initialization sequence\n```\n\n## Anti-Patterns to Avoid\n\n❌ **Don't** attempt to debug agent reasoning when 0 iterations occurred\n❌ **Don't** assume the task instructions were unclear (agent never saw them)\n❌ **Don't** retry with modified prompts before checking system health\n❌ **Don't** categorize as \"agent performance issue\"\n\n## Integration with Failure Tracking\n\nWhen logging failures, Tag zero-iteration failures distinctly:\n\n```json\n{\n  \"failure_id\": \"xyz123\",\n  \"failure_mode\": \"pre_execution\",\n  \"iteration_count\": 0,\n  \"requires_system_review\": true,\n  \"agent_actionable\": false\n}\n```","# Zero-Iteration Failure Analysis\n\nThis skill provides a workflow for detecting and responding to agent failures that occur before any iterations are executed. These failures indicate system-level problems rather than task execution issues.\n\n## When to Apply\n\nUse this skill when analyzing agent execution results and you observe:\n- **0 iterations** reported in the execution summary\n- **No tool invocations** in the conversation log\n- **No artifacts created** (no files, outputs, or intermediate results)\n- **Error message** present but no agent reasoning visible\n\n## Identification Checklist\n\nA zero-iteration failure is confirmed when **ALL** of the following are true:\n\n```\n[ ] Iteration count = 0\n[ ] Tool usage count = 0  \n[ ] No conversation log beyond initial instruction\n[ ] Error\u002Fself-report indicates failure before execution began\n```\n\n## Failure Mode Classification\n\n| Indicator | Failure Type | Investigation Level |\n|-----------|--------------|---------------------|\n| 0 iterations, 0 tools | Pre-execution | System-level |\n| 1+ iterations, error mid-task | Execution | Agent-level |\n| 1+ iterations, wrong output | Reasoning | Agent-level |\n\n## Investigation Steps\n\n### Step 1: Confirm Zero-Iteration Status\n\n```python\ndef is_zero_iteration_failure(execution_result):\n    \"\"\"Check if failure occurred before any agent iterations.\"\"\"\n    return (\n        execution_result.get('iterations', 0) == 0 and\n        execution_result.get('tool_calls', []) == [] and\n        execution_result.get('artifacts', []) == []\n    )\n```\n\n### Step 2: Extract Error Context\n\nExamine any error message or self-report for clues:\n- **Initialization errors**: Environment setup, dependency missing, config invalid\n- **Prompt parsing errors**: Malformed instruction, missing required fields\n- **Resource errors**: Memory limits, timeout before start, permission denied\n\n### Step 3: Route to Appropriate Investigation\n\n```\nIF zero-iteration failure detected:\n    → Escalate to SYSTEM investigation\n    → Do NOT attempt agent-level debugging\n    → Check: environment, dependencies, prompt format, resource limits\nELSE:\n    → Proceed with standard agent failure analysis\n```\n\n### Step 4: Document the Failure Mode\n\nRecord the failure with appropriate categorization:\n\n```yaml\nfailure_analysis:\n  type: zero-iteration\n  severity: high\n  investigation_level: system\n  agent_debugging_appropriate: false\n  recommended_actions:\n    - Check execution environment health\n    - Verify prompt\u002Finput formatting\n    - Review system logs for initialization errors\n    - Validate resource availability\n```\n\n## Common Causes and Resolutions\n\n| Cause | Symptoms | Resolution |\n|-------|----------|------------|\n| Environment crash | Immediate error, no context | Restart environment, check dependencies |\n| Prompt parse failure | Error mentions instruction format | Validate input schema, fix formatting |\n| Resource exhaustion | Timeout or memory error before start | Increase limits, optimize initialization |\n| Permission denied | Access error on startup | Check file\u002Fsystem permissions |\n\n## Escalation Criteria\n\nImmediately flag for system-level review when:\n- Zero-iteration failures occur repeatedly (>2 in same session)\n- Error messages indicate infrastructure issues\n- Multiple agents fail with same zero-iteration pattern\n\n## Example Analysis\n\n```\nEXECUTION SUMMARY:\n- Iterations: 0\n- Tools Used: None\n- Artifacts: None\n- Status: Failed\n- Error: \"Agent initialization failed: missing required config\"\n\nANALYSIS:\n✓ Zero-iteration failure detected\n✓ Pre-execution failure mode confirmed\n→ Action: Escalate to system investigation\n→ Do NOT debug agent reasoning (no reasoning occurred)\n→ Check: config loading, environment variables, initialization sequence\n```\n\n## Anti-Patterns to Avoid\n\n❌ **Don't** attempt to debug agent reasoning when 0 iterations occurred\n❌ **Don't** assume the task instructions were unclear (agent never saw them)\n❌ **Don't** retry with modified prompts before checking system health\n❌ **Don't** categorize as \"agent performance issue\"\n\n## Integration with Failure Tracking\n\nWhen logging failures, Tag zero-iteration failures distinctly:\n\n```json\n{\n  \"failure_id\": \"xyz123\",\n  \"failure_mode\": \"pre_execution\",\n  \"iteration_count\": 0,\n  \"requires_system_review\": true,\n  \"agent_actionable\": false\n}\n```",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fzero-iteration-failure-analysis","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill zero-iteration-failure-analysis",{"tool":45,"command":46},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill zero-iteration-failure-analysis",{"tool":48,"command":49},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill zero-iteration-failure-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fzero-iteration-failure-analysis\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},".skill_id","OTHER","其他",45,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fzero-iteration-failure-analysis\u002F.skill_id",[60,85,101,110,140,156],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":28},"01M6XCCXD3NCM2YKR3WNGBASPC","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","files","only","template","file","python",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":28},"01M6XCCT7E3J922Q345PBGSHPN","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[92,93,68,83,94,84,95,96,97,98,99,82,100,27,72,75,77],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":28},"01M6XCCMQX1R8B6FECWB3P63T7","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[108,68,72,109,77,96,82,83,84,75],"write special chars heredoc","shell",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"publishedAt":28},"01M6XCCG41M994JJEX6VN52PEP","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[122,123,124,125,126,70,127,128,129,130,131,75,132,133,134,135,136,137,138,139],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":28},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[147,148,149,150,75,151,27,152,153,154,155],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":28},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[163,164,165,166,167,168,83,23,169,170],"directory","verify directory structure","structure","verify","access","first","diagnose","file access"]