[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HX5N6S401V8RFASSE5FE7E":3,"skill-same:01M6HX5N6S401V8RFASSE5FE7E":74},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6HX5N6S401V8RFASSE5FE7E","fallback-doc-with-delegation",null,"Generate professional documents after tool failures using shell_agent for complex formats or write_file for simple text\u002Fmarkdown","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-enhanced\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"fallback doc with delegation","delegation","doc","with","fallback","text","for","formats","professional","simple","write","documents","tool","markdown","shell","file","generate","2026-11-10 10:12:30",false,"---\nname: fallback-doc-with-delegation\ndescription: Generate professional documents after tool failures using shell_agent for complex formats or write_file for simple text\u002Fmarkdown\n---\n\n# Fallback Document Generation with Delegation\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 using the most appropriate available method—either `shell_agent` for complex formats or `write_file` for simple text.\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: Choose the Appropriate Fallback Method\n\n**Critical Decision**: Select between `shell_agent` and `write_file` based on document complexity:\n\n| Use `shell_agent` when... | Use `write_file` when... |\n|---------------------------|--------------------------|\n| Generating PDFs or formatted documents | Creating simple markdown\u002Ftext files |\n| Complex layout or styling needed | Plain structured content is sufficient |\n| External libraries required (reportlab, pandoc) | No special formatting libraries needed |\n| Multi-step generation process | Single-pass content generation |\n| Verification\u002Fvalidation needed | Direct file creation is adequate |\n\n**Decision Tree**:\n```\nIs the output a PDF or complex formatted document?\n├── YES → Use shell_agent (delegates to skilled agent)\n└── NO → Is it markdown or plain text?\n    ├── YES → Use write_file (direct content generation)\n    └── NO → Use shell_agent (handles uncertainty)\n```\n\n### Step 3A: Execute with shell_agent (Complex Documents)\n\nFor PDFs and complex formatting:\n\n```python\n# Delegate to shell_agent with clear task description\nshell_agent(\n    task=\"Generate a professional [document type] about [topic]. \"\n         \"Use appropriate libraries (e.g., reportlab for PDFs). \"\n         \"Include: [list key sections\u002Frequirements]. \"\n         \"Save to working directory as [filename].\"\n)\n```\n\n**Advantages of shell_agent**:\n- Agent autonomously handles library selection and usage\n- Automatically retries and fixes errors\n- Can use multiple tools internally (run_shell, execute_code_sandbox)\n- Validates output before completion\n\n**Example**:\n```python\nshell_agent(\n    task=\"Create a 1-page SBAR (Situation-Background-Assessment-Recommendation) \"\n         \"template PDF with 4 sections. Each section should have guiding points \"\n         \"and blank lined spaces for user input. Use reportlab library. \"\n         \"Save as SBAR_template.pdf in current directory.\"\n)\n```\n\n### Step 3B: Execute with write_file (Simple Documents)\n\nFor markdown and plain text:\n\n```python\n# Generate content with embedded domain knowledge\nreport_content = f\"\"\"# [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\nwrite_file(path=\"output\u002Freport.md\", content=report_content)\n```\n\n### Step 4: Structure Content Professionally\n\nRegardless of method, ensure professional organization:\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 5: 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 6: Validate Output\n\n```python\n# For shell_agent: verify the output exists and is valid\nlist_dir(path=\".\")  # Confirm file was created\n\n# For PDFs, optionally verify with pdfinfo via run_shell\n# For markdown, optionally read to confirm content\n\n# For write_file: confirm file exists\nlist_dir(path=\".\")  # Confirm file exists\n```\n\n## Code Example\n\n```python\n# Complete detection and pivot pattern\ndef generate_fallback_document(task_goal, output_format=\"markdown\"):\n    # After detecting tool failures:\n    \n    # Step 1: Choose method based on format\n    if output_format == \"pdf\" or \"complex\" in task_goal:\n        # Use shell_agent for complex formats\n        shell_agent(\n            task=f\"Generate a professional {output_format} document about \"\n                 f\"{task_goal}. Use appropriate libraries. Include executive \"\n                 f\"summary, main content, limitations, and recommendations. \"\n                 f\"Save to working directory.\"\n        )\n        return \"Document generated via shell_agent delegation\"\n    \n    else:\n        # Use write_file for simple formats\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        write_file(path=\"generated_report.md\", content=report_content)\n        return \"Report generated with write_file\"\n```\n\n## Best Practices\n\n| Do | Don't |\n|----|-------|\n| Choose method based on document complexity | Default to write_file for PDFs without consideration |\n| Delegate complex formatting to shell_agent | 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| Validate the generated output | Assume success without verification |\n\n## Common Pitfalls\n\n1. **Wrong tool selection**: Using write_file for PDF generation instead of delegating to shell_agent\n2. **Over-apologizing**: Acknowledge limitations once, then deliver value\n3. **Under-delivering**: A well-structured partial report beats no report\n4. **Misrepresenting certainty**: Use appropriate hedging language\n5. **Skipping validation**: Always confirm the file was created successfully\n\n## Success Criteria\n\nThe skill is successfully applied when:\n\n- [ ] Document is generated despite tool failures\n- [ ] Appropriate method chosen (shell_agent for complex, write_file for simple)\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\n\n## Method Comparison\n\n| Aspect | shell_agent | write_file |\n|--------|-------------|------------|\n| Best for | PDFs, complex layouts, multi-step generation | Markdown, plain text, single-pass content |\n| Error handling | Autonomous retry and fix | Manual error handling required |\n| Library access | Full library ecosystem | Content-only (no external libs) |\n| Processing time | Longer (agent reasoning) | Faster (direct write) |\n| Verification | Built-in validation | Manual verification needed |\n| Cost | Higher (agent execution) | Lower (simple operation) |\n\n## Decision Checklist\n\nBefore selecting method, ask:\n\n1. Is the output format PDF or other binary format? → **shell_agent**\n2. Does it require external libraries (reportlab, pandoc, etc.)? → **shell_agent**\n3. Is it markdown or plain text only? → **write_file**\n4. Does it need multi-step processing or validation? → **shell_agent**\n5. Is quick, simple content generation sufficient? → **write_file**\n","# Fallback Document Generation with Delegation\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 using the most appropriate available method—either `shell_agent` for complex formats or `write_file` for simple text.\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: Choose the Appropriate Fallback Method\n\n**Critical Decision**: Select between `shell_agent` and `write_file` based on document complexity:\n\n| Use `shell_agent` when... | Use `write_file` when... |\n|---------------------------|--------------------------|\n| Generating PDFs or formatted documents | Creating simple markdown\u002Ftext files |\n| Complex layout or styling needed | Plain structured content is sufficient |\n| External libraries required (reportlab, pandoc) | No special formatting libraries needed |\n| Multi-step generation process | Single-pass content generation |\n| Verification\u002Fvalidation needed | Direct file creation is adequate |\n\n**Decision Tree**:\n```\nIs the output a PDF or complex formatted document?\n├── YES → Use shell_agent (delegates to skilled agent)\n└── NO → Is it markdown or plain text?\n    ├── YES → Use write_file (direct content generation)\n    └── NO → Use shell_agent (handles uncertainty)\n```\n\n### Step 3A: Execute with shell_agent (Complex Documents)\n\nFor PDFs and complex formatting:\n\n```python\n# Delegate to shell_agent with clear task description\nshell_agent(\n    task=\"Generate a professional [document type] about [topic]. \"\n         \"Use appropriate libraries (e.g., reportlab for PDFs). \"\n         \"Include: [list key sections\u002Frequirements]. \"\n         \"Save to working directory as [filename].\"\n)\n```\n\n**Advantages of shell_agent**:\n- Agent autonomously handles library selection and usage\n- Automatically retries and fixes errors\n- Can use multiple tools internally (run_shell, execute_code_sandbox)\n- Validates output before completion\n\n**Example**:\n```python\nshell_agent(\n    task=\"Create a 1-page SBAR (Situation-Background-Assessment-Recommendation) \"\n         \"template PDF with 4 sections. Each section should have guiding points \"\n         \"and blank lined spaces for user input. Use reportlab library. \"\n         \"Save as SBAR_template.pdf in current directory.\"\n)\n```\n\n### Step 3B: Execute with write_file (Simple Documents)\n\nFor markdown and plain text:\n\n```python\n# Generate content with embedded domain knowledge\nreport_content = f\"\"\"# [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\nwrite_file(path=\"output\u002Freport.md\", content=report_content)\n```\n\n### Step 4: Structure Content Professionally\n\nRegardless of method, ensure professional organization:\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 5: 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 6: Validate Output\n\n```python\n# For shell_agent: verify the output exists and is valid\nlist_dir(path=\".\")  # Confirm file was created\n\n# For PDFs, optionally verify with pdfinfo via run_shell\n# For markdown, optionally read to confirm content\n\n# For write_file: confirm file exists\nlist_dir(path=\".\")  # Confirm file exists\n```\n\n## Code Example\n\n```python\n# Complete detection and pivot pattern\ndef generate_fallback_document(task_goal, output_format=\"markdown\"):\n    # After detecting tool failures:\n    \n    # Step 1: Choose method based on format\n    if output_format == \"pdf\" or \"complex\" in task_goal:\n        # Use shell_agent for complex formats\n        shell_agent(\n            task=f\"Generate a professional {output_format} document about \"\n                 f\"{task_goal}. Use appropriate libraries. Include executive \"\n                 f\"summary, main content, limitations, and recommendations. \"\n                 f\"Save to working directory.\"\n        )\n        return \"Document generated via shell_agent delegation\"\n    \n    else:\n        # Use write_file for simple formats\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        write_file(path=\"generated_report.md\", content=report_content)\n        return \"Report generated with write_file\"\n```\n\n## Best Practices\n\n| Do | Don't |\n|----|-------|\n| Choose method based on document complexity | Default to write_file for PDFs without consideration |\n| Delegate complex formatting to shell_agent | 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| Validate the generated output | Assume success without verification |\n\n## Common Pitfalls\n\n1. **Wrong tool selection**: Using write_file for PDF generation instead of delegating to shell_agent\n2. **Over-apologizing**: Acknowledge limitations once, then deliver value\n3. **Under-delivering**: A well-structured partial report beats no report\n4. **Misrepresenting certainty**: Use appropriate hedging language\n5. **Skipping validation**: Always confirm the file was created successfully\n\n## Success Criteria\n\nThe skill is successfully applied when:\n\n- [ ] Document is generated despite tool failures\n- [ ] Appropriate method chosen (shell_agent for complex, write_file for simple)\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\n\n## Method Comparison\n\n| Aspect | shell_agent | write_file |\n|--------|-------------|------------|\n| Best for | PDFs, complex layouts, multi-step generation | Markdown, plain text, single-pass content |\n| Error handling | Autonomous retry and fix | Manual error handling required |\n| Library access | Full library ecosystem | Content-only (no external libs) |\n| Processing time | Longer (agent reasoning) | Faster (direct write) |\n| Verification | Built-in validation | Manual verification needed |\n| Cost | Higher (agent execution) | Lower (simple operation) |\n\n## Decision Checklist\n\nBefore selecting method, ask:\n\n1. Is the output format PDF or other binary format? → **shell_agent**\n2. Does it require external libraries (reportlab, pandoc, etc.)? → **shell_agent**\n3. Is it markdown or plain text only? → **write_file**\n4. Does it need multi-step processing or validation? → **shell_agent**\n5. Is quick, simple content generation sufficient? → **write_file**\n",{"name":5,"description":7},"main","6b84b0689ca0d9e7b1e4061188ff6b60758e0f8a","openspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fwrite-file-fallback-report-enhanced",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add HKUDS\u002FAgentPilot --skill fallback-doc-with-delegation",{"tool":60,"command":61},"bunx","bunx skills add HKUDS\u002FAgentPilot --skill fallback-doc-with-delegation",{"tool":63,"command":64},"pnpm","pnpm dlx skills add HKUDS\u002FAgentPilot --skill fallback-doc-with-delegation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fwrite-file-fallback-report-enhanced\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},".skill_id","OTHER","其他",49,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fwrite-file-fallback-report-enhanced\u002F.skill_id",[75,94,113,134,156,177],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":41},"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",[],[77,82,83,27,84,85,86,87,88,89,90,91,92,93],"prepare","requests","missing","installation","rsi","up","use","user","work","SET","run","experiments",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":41},"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",[],[96,101,102,103,104,105,106,107,108,109,110,111,112],"memory","review","auto","openspace","changes","facts","detect","entries","local","conflicts","stale","duplicates",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":41},"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",[119],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[121,122,123,104,124,125,126,127,128,129,130,131,132,133],"skill discovery","discovery","reusable","step by step","tokens","packages","help","cloud","reliability","capabilities","browse","search","Tools",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":41},"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",[140],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[142,143,144,104,145,146,147,148,149,123,103,88,150,36,151,30,152,153,154,155],"delegate","task","delegate task","time","improve","desktop automation","worker","community","autonomous","stack","share","tasks","automation","MCP",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":41},"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",[],[163,34,164,165,166,167,168,169,39,170,171,172,173,174,30,175,176],"write special chars ts check","check","type","files","filters","only","template","python","typescript","output","Existing","type-checking","errors","script",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":41},"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",[],[184,185,34,27,30,176,186,187,188,189,190,169,39,191,192,170],"write special chars readback","readback","helper","post","via","scripts","read","verification","cleanup"]