[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XC50CWHZKF25C134C0B2B4":3,"skill-same:01M6XC50CWHZKF25C134C0B2B4":70},{"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":22,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":13,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6XC50CWHZKF25C134C0B2B4","write-file-fallback-report",null,"Generate professional documents using write_file when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval","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\u002Fwrite-file-fallback-report\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"report","file","write","fallback","write file fallback report","documents","generate","data","knowledge","embedded","domain","professional","sources","retrieval","data sources","when","2026-11-10 10:12:30",false,"---\nname: write-file-fallback-report\ndescription: Generate professional documents using write_file when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval\n---\n\n# Write-File Fallback Report Generation\n\n## When to Use This Skill\n\nUse this workflow when attempting to generate a document or report, but **multiple primary data source tools fail simultaneously**:\n\n- `read_file` returns binary\u002Fimage data instead of text (common with PDFs)\n- `search_web` returns errors or no results\n- `execute_code_sandbox` fails unexpectedly\n- Other data retrieval tools are unavailable\n\n**Key insight**: Rather than getting stuck on failed data retrieval, pivot immediately to generating the document directly with `write_file` using professionally structured content and embedded domain knowledge.\n\n## Step-by-Step Instructions\n\n### Step 1: Detect Tool Failure Pattern\n\nRecognize when you're in a fallback scenario:\n\n```\nTOOL_FAILURE_INDICATORS = [\n    \"read_file returns binary or image data\",\n    \"search_web returns unknown error or empty results\",\n    \"execute_code_sandbox fails repeatedly\",\n    \"Multiple consecutive tool failures on data retrieval\"\n]\n```\n\n**Decision point**: If 2+ indicators are present, proceed to Step 2.\n\n### Step 2: Pivot to Write-File-First Approach\n\n**Stop attempting** to fix the failing tools. Instead:\n\n1. Acknowledge the limitation briefly in your output\n2. Commit to generating the document with available knowledge\n3. Use `write_file` as your **primary** tool (not a last resort)\n\n### Step 3: Structure the Document Professionally\n\nCreate a well-organized markdown document with:\n\n```markdown\n# [Document Title]\n\n## Executive Summary\n[Brief overview of key findings\u002Fcontent]\n\n## Background\n[Context and scope - use embedded knowledge]\n\n## Main Content\n[Organized sections with headers, lists, tables as appropriate]\n\n## Limitations & Notes\n[Transparent about data source limitations if relevant]\n\n## Recommendations\u002FNext Steps\n[Actionable guidance based on available information]\n```\n\n### Step 4: Leverage Embedded Domain Knowledge\n\nWhen external data is unavailable:\n\n- Use **general domain knowledge** appropriately\n- Clearly distinguish between verified facts and general guidance\n- Include **actionable frameworks** rather than specific unverified data\n- Add **placeholder notes** where specific data would enhance the document\n\nExample:\n```markdown\n> **Note**: Specific [metric\u002Fdata point] would typically be sourced from \n> [expected source]. The guidance below reflects established best practices \n> in this domain.\n```\n\n### Step 5: Execute and Validate\n\n```python\n# Example execution pattern\nwrite_file(\n    path=\"output\u002Freport.md\",\n    content=professionally_structured_markdown\n)\n# Verify the file was created successfully\nlist_dir(path=\".\")  # Confirm file exists\n```\n\n## Code Example\n\n```python\n# Detection and pivot pattern\ndef detect_and_pivot(task_goal):\n    # After detecting tool failures:\n    \n    report_content = f\"\"\"# {task_goal} Report\n\n## Executive Summary\nThis report was generated using established domain knowledge due to \ntemporary unavailability of primary data sources.\n\n## Key Frameworks and Guidance\n[Structured content with headers, bullets, tables]\n\n## Limitations\n- Specific data points from [expected sources] were unavailable\n- Recommendations based on general best practices\n\n## Action Items\n1. [Concrete step 1]\n2. [Concrete step 2]\n\"\"\"\n    \n    write_file(path=\"generated_report.md\", content=report_content)\n    return \"Report generated successfully with embedded knowledge\"\n```\n\n## Best Practices\n\n| Do | Don't |\n|----|-------|\n| Pivot quickly after 2+ tool failures | Keep retrying failing tools 5+ times |\n| Be transparent about limitations | Claim unverified specifics as facts |\n| Provide actionable frameworks | Leave the task incomplete |\n| Use professional document structure | Output unstructured text walls |\n| Include next-step recommendations | End without clear guidance |\n\n## Common Pitfalls\n\n1. **Over-apologizing**: Acknowledge limitations once, then deliver value\n2. **Under-delivering**: A well-structured partial report beats no report\n3. **Misrepresenting certainty**: Use appropriate hedging language\n4. **Skipping structure**: Professional formatting increases usability\n\n## Success Criteria\n\nThe skill is successfully applied when:\n\n- [ ] Document is generated despite tool failures\n- [ ] Content is professionally structured (headers, sections, lists)\n- [ ] Limitations are transparently noted\n- [ ] Actionable guidance is provided\n- [ ] File is successfully created and verified","# Write-File Fallback Report Generation\n\n## When to Use This Skill\n\nUse this workflow when attempting to generate a document or report, but **multiple primary data source tools fail simultaneously**:\n\n- `read_file` returns binary\u002Fimage data instead of text (common with PDFs)\n- `search_web` returns errors or no results\n- `execute_code_sandbox` fails unexpectedly\n- Other data retrieval tools are unavailable\n\n**Key insight**: Rather than getting stuck on failed data retrieval, pivot immediately to generating the document directly with `write_file` using professionally structured content and embedded domain knowledge.\n\n## Step-by-Step Instructions\n\n### Step 1: Detect Tool Failure Pattern\n\nRecognize when you're in a fallback scenario:\n\n```\nTOOL_FAILURE_INDICATORS = [\n    \"read_file returns binary or image data\",\n    \"search_web returns unknown error or empty results\",\n    \"execute_code_sandbox fails repeatedly\",\n    \"Multiple consecutive tool failures on data retrieval\"\n]\n```\n\n**Decision point**: If 2+ indicators are present, proceed to Step 2.\n\n### Step 2: Pivot to Write-File-First Approach\n\n**Stop attempting** to fix the failing tools. Instead:\n\n1. Acknowledge the limitation briefly in your output\n2. Commit to generating the document with available knowledge\n3. Use `write_file` as your **primary** tool (not a last resort)\n\n### Step 3: Structure the Document Professionally\n\nCreate a well-organized markdown document with:\n\n```markdown\n# [Document Title]\n\n## Executive Summary\n[Brief overview of key findings\u002Fcontent]\n\n## Background\n[Context and scope - use embedded knowledge]\n\n## Main Content\n[Organized sections with headers, lists, tables as appropriate]\n\n## Limitations & Notes\n[Transparent about data source limitations if relevant]\n\n## Recommendations\u002FNext Steps\n[Actionable guidance based on available information]\n```\n\n### Step 4: Leverage Embedded Domain Knowledge\n\nWhen external data is unavailable:\n\n- Use **general domain knowledge** appropriately\n- Clearly distinguish between verified facts and general guidance\n- Include **actionable frameworks** rather than specific unverified data\n- Add **placeholder notes** where specific data would enhance the document\n\nExample:\n```markdown\n> **Note**: Specific [metric\u002Fdata point] would typically be sourced from \n> [expected source]. The guidance below reflects established best practices \n> in this domain.\n```\n\n### Step 5: Execute and Validate\n\n```python\n# Example execution pattern\nwrite_file(\n    path=\"output\u002Freport.md\",\n    content=professionally_structured_markdown\n)\n# Verify the file was created successfully\nlist_dir(path=\".\")  # Confirm file exists\n```\n\n## Code Example\n\n```python\n# Detection and pivot pattern\ndef detect_and_pivot(task_goal):\n    # After detecting tool failures:\n    \n    report_content = f\"\"\"# {task_goal} Report\n\n## Executive Summary\nThis report was generated using established domain knowledge due to \ntemporary unavailability of primary data sources.\n\n## Key Frameworks and Guidance\n[Structured content with headers, bullets, tables]\n\n## Limitations\n- Specific data points from [expected sources] were unavailable\n- Recommendations based on general best practices\n\n## Action Items\n1. [Concrete step 1]\n2. [Concrete step 2]\n\"\"\"\n    \n    write_file(path=\"generated_report.md\", content=report_content)\n    return \"Report generated successfully with embedded knowledge\"\n```\n\n## Best Practices\n\n| Do | Don't |\n|----|-------|\n| Pivot quickly after 2+ tool failures | Keep retrying failing tools 5+ times |\n| Be transparent about limitations | Claim unverified specifics as facts |\n| Provide actionable frameworks | Leave the task incomplete |\n| Use professional document structure | Output unstructured text walls |\n| Include next-step recommendations | End without clear guidance |\n\n## Common Pitfalls\n\n1. **Over-apologizing**: Acknowledge limitations once, then deliver value\n2. **Under-delivering**: A well-structured partial report beats no report\n3. **Misrepresenting certainty**: Use appropriate hedging language\n4. **Skipping structure**: Professional formatting increases usability\n\n## Success Criteria\n\nThe skill is successfully applied when:\n\n- [ ] Document is generated despite tool failures\n- [ ] Content is professionally structured (headers, sections, lists)\n- [ ] Limitations are transparently noted\n- [ ] Actionable guidance is provided\n- [ ] File is successfully created and verified",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fwrite-file-fallback-report","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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill write-file-fallback-report",{"tool":56,"command":57},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill write-file-fallback-report",{"tool":59,"command":60},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill write-file-fallback-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fwrite-file-fallback-report\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},".skill_id","OTHER","其他",40,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fwrite-file-fallback-report\u002F.skill_id",[71,94,111,120,147,163],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":39},"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",[],[78,25,79,80,81,82,83,84,85,86,87,88,89,90,91,92,24,93],"check","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","files","only","template","python",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":39},"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",[],[101,102,25,24,103,93,104,105,106,107,108,92,109,110,82,85,87],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification","with",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":39},"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",[],[118,25,82,119,87,105,92,24,93,85],"write special chars heredoc","shell",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":129,"publishedAt":39},"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",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000033","数据分析师",[130,131,132,133,134,80,135,136,137,138,139,85,140,141,142,143,144,145,146,30],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":39},"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",[],[154,155,156,157,85,158,110,159,160,161,162],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":39},"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",[],[170,171,172,173,174,175,24,176,177,178],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]