[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HX5SCREBDAFWQ89P8AJF19":3,"skill-same:01M6HX5SCREBDAFWQ89P8AJF19":71},{"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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6HX5SCREBDAFWQ89P8AJF19","write-file-fallback-report",null,"Generate professional documents using write_file when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval","HKUDS\u002FAgentPilot","HKUDS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F118165258?v=4","01M6HW8VRNZP64G0P4MVJW2KKQ","✨Data Intelligence Lab@HKU✨","01M6HW8VWZVHBRHYH3T330PFWV",8029,"MIT","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fwrite-file-fallback-report\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"report","file","write","fallback","write file fallback report","documents","generate","data","knowledge","embedded","domain","professional","sources","retrieval","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","6b84b0689ca0d9e7b1e4061188ff6b60758e0f8a","openspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fwrite-file-fallback-report",944,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot","https:\u002F\u002Fgithub.com\u002FHKUDS","https:\u002F\u002Fsites.google.com\u002Fview\u002Fchaoh","2026-11-12 22:26:39",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add HKUDS\u002FAgentPilot --skill write-file-fallback-report",{"tool":57,"command":58},"bunx","bunx skills add HKUDS\u002FAgentPilot --skill write-file-fallback-report",{"tool":60,"command":61},"pnpm","pnpm dlx skills add HKUDS\u002FAgentPilot --skill write-file-fallback-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fwrite-file-fallback-report\u002FSKILL.md",true,[65],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},".skill_id","OTHER","其他",40,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fwrite-file-fallback-report\u002F.skill_id",[72,92,111,136,160,181],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":38},"01M6HYB297NDABRERJRVG0K8R0","agentpilot","Set up AgentPilot and use its single entry to prepare missing inputs and run configured RSI experiments. Use when the user requests AgentPilot installation or work with AgentPilot.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fplugins\u002Fagentpilot\u002Fskills\u002Fagentpilot\u002FSKILL.md",[],[74,79,80,81,82,83,84,85,86,87,88,89,90,91],"prepare","requests","with","missing","installation","rsi","up","use","user","work","SET","run","experiments",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":38},"01M6HYAYWXTTE1J7DJM0MFNQ4H","remember","Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fskills\u002Fremember\u002FSKILL.md",[],[94,99,100,101,102,103,104,105,106,107,108,109,110],"memory","review","auto","openspace","changes","facts","detect","entries","local","conflicts","stale","duplicates",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":122,"publishedAt":38},"01M6HYAVMPM4SBDV60R2B5HPV8","skill-discovery","Search reusable OpenSpace skills locally, and browse cloud packages step by step when a cloud skill may help. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fhost_skills\u002Fskill-discovery\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[123,124,125,102,126,127,128,129,130,131,132,133,134,135],"skill discovery","discovery","reusable","step by step","tokens","packages","help","cloud","reliability","capabilities","browse","search","Tools",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":38},"01M6HYAR811B3RB0M50RBEDGN6","delegate-task","Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fhost_skills\u002Fdelegate-task\u002FSKILL.md",[142],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[144,145,146,102,147,148,149,150,151,125,101,86,152,153,154,155,156,157,158,159],"delegate","task","delegate task","time","improve","desktop automation","worker","community","autonomous","tool","stack","for","share","tasks","automation","MCP",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":38},"01M6HYAM9FSGV6E52AYENDQXYH","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\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[167,26,168,169,170,171,172,173,25,174,175,176,177,178,155,179,180],"write special chars ts check","check","type","files","filters","only","template","python","typescript","output","Existing","type-checking","errors","script",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":38},"01M6HYAH05HGV7SVWSVR8PJRQD","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\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[188,189,26,81,155,180,190,191,192,193,194,173,25,195,196,174],"write special chars readback","readback","helper","post","via","scripts","read","verification","cleanup"]