[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HWAR3G0MMZH3ZBVFYC6DVQ":3,"skill-same:01M6HWAR3G0MMZH3ZBVFYC6DVQ":68},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6HWAR3G0MMZH3ZBVFYC6DVQ","code-execution-fallback-e81068",null,"Fallback workflow for executing Python code when execute_code_sandbox fails repeatedly","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\u002Fcode-execution-fallback-e81068\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34],"code","execution","fallback","code execution","code execution fallback e81068","python","sandbox","workflow","execute","python code","for","2026-11-10 10:12:30",false,"---\nname: code-execution-fallback-e81068\ndescription: Fallback workflow for executing Python code when execute_code_sandbox fails repeatedly\n---\n\n# Code Execution Fallback Workflow\n\n## When to Use\n\nUse this skill when `execute_code_sandbox` fails repeatedly (2+ attempts) with unknown, persistent, or unexplained errors. This fallback approach uses `write_file` + `run_shell` to save Python scripts to disk and execute them via command line, which has proven more reliable in certain failure scenarios.\n\n## Step-by-Step Instructions\n\n### Step 1: Detect Repeated Failures\n\nMonitor `execute_code_sandbox` attempts. After 2 consecutive failures with errors like:\n- \"Unknown error\"\n- Timeout errors\n- Unexplained execution failures\n- Sandbox environment issues\n\nSwitch to the fallback workflow immediately.\n\n### Step 2: Write the Python Script to File\n\nUse `write_file` to save your Python code as a `.py` file in the working directory:\n\n```python\nwrite_file(\n    path=\"script.py\",\n    content=\"\"\"\nimport sys\nimport json\n\n# Your Python code here\ndef main():\n    # Your logic\n    result = {\"status\": \"success\", \"data\": \"example\"}\n    print(json.dumps(result))\n\nif __name__ == \"__main__\":\n    main()\n\"\"\"\n)\n```\n\n**Tips:**\n- Use clear, self-contained code that doesn't rely on sandbox-specific paths\n- Include error handling and informative print statements\n- Save output to files if needed for later retrieval\n\n### Step 3: Execute via Shell\n\nUse `run_shell` to execute the Python script via command line:\n\n```python\nrun_shell(\n    command=\"python3 script.py\",\n    timeout=60  # Adjust timeout as needed\n)\n```\n\n**Alternative commands:**\n- `python script.py` - if python3 alias isn't available\n- `python3 -u script.py` - for unbuffered output\n- `python3 script.py arg1 arg2` - with arguments\n\n### Step 4: Verify Output and Results\n\nCheck the stdout\u002Fstderr from `run_shell` to:\n- Confirm execution succeeded (exit code 0)\n- Inspect printed output or results\n- Identify any new errors (different from sandbox errors)\n\nIf the script writes output files, use `read_file` to retrieve results.\n\n### Step 5: Clean Up (Optional)\n\nRemove temporary script files if they won't be reused:\n\n```python\nrun_shell(command=\"rm script.py\")\n```\n\n## Complete Example\n\n**Scenario:** `execute_code_sandbox` failed twice while trying to process data.\n\n**Fallback execution:**\n\n```python\n# Step 1: Write the processing script\nwrite_file(\n    path=\"process_data.py\",\n    content=\"\"\"\nimport pandas as pd\nimport json\n\ndef process():\n    data = [1, 2, 3, 4, 5]\n    result = {\"sum\": sum(data), \"count\": len(data)}\n    print(json.dumps(result))\n    \n    # Also save to file for reliability\n    with open(\"result.json\", \"w\") as f:\n        json.dump(result, f)\n\nif __name__ == \"__main__\":\n    process()\n\"\"\"\n)\n\n# Step 2: Execute via shell\noutput = run_shell(command=\"python3 process_data.py\")\n\n# Step 3: Read results from file\nresults = read_file(file_path=\"result.json\", filetype=\"json\")\n```\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| `python3: command not found` | Try `python` instead, or check available interpreters with `which python` |\n| Permission denied | Ensure the working directory is writable; `write_file` creates files in workspace by default |\n| Module not found | Install dependencies via `run_shell(command=\"pip install package_name\")` before execution |\n| Script hangs | Increase timeout parameter in `run_shell` |\n| Output too long | Redirect output to file within the script and read it separately |\n\n## Best Practices\n\n1. **Always include error handling** in scripts to capture failures gracefully\n2. **Write results to files** in addition to printing, for reliable retrieval\n3. **Use descriptive filenames** to avoid conflicts (e.g., `task_specific_script.py`)\n4. **Keep scripts self-contained** - avoid dependencies on sandbox environment variables\n5. **Log execution details** for debugging: `print(f\"Step X complete: {value}\")`\n\n## When NOT to Use This Fallback\n\n- When sandbox isolation is required for security\n- When the task explicitly requires `execute_code_sandbox`\n- When `execute_code_sandbox` succeeds consistently (no need to add complexity)\n- When working with sensitive data that shouldn't persist to disk","# Code Execution Fallback Workflow\n\n## When to Use\n\nUse this skill when `execute_code_sandbox` fails repeatedly (2+ attempts) with unknown, persistent, or unexplained errors. This fallback approach uses `write_file` + `run_shell` to save Python scripts to disk and execute them via command line, which has proven more reliable in certain failure scenarios.\n\n## Step-by-Step Instructions\n\n### Step 1: Detect Repeated Failures\n\nMonitor `execute_code_sandbox` attempts. After 2 consecutive failures with errors like:\n- \"Unknown error\"\n- Timeout errors\n- Unexplained execution failures\n- Sandbox environment issues\n\nSwitch to the fallback workflow immediately.\n\n### Step 2: Write the Python Script to File\n\nUse `write_file` to save your Python code as a `.py` file in the working directory:\n\n```python\nwrite_file(\n    path=\"script.py\",\n    content=\"\"\"\nimport sys\nimport json\n\n# Your Python code here\ndef main():\n    # Your logic\n    result = {\"status\": \"success\", \"data\": \"example\"}\n    print(json.dumps(result))\n\nif __name__ == \"__main__\":\n    main()\n\"\"\"\n)\n```\n\n**Tips:**\n- Use clear, self-contained code that doesn't rely on sandbox-specific paths\n- Include error handling and informative print statements\n- Save output to files if needed for later retrieval\n\n### Step 3: Execute via Shell\n\nUse `run_shell` to execute the Python script via command line:\n\n```python\nrun_shell(\n    command=\"python3 script.py\",\n    timeout=60  # Adjust timeout as needed\n)\n```\n\n**Alternative commands:**\n- `python script.py` - if python3 alias isn't available\n- `python3 -u script.py` - for unbuffered output\n- `python3 script.py arg1 arg2` - with arguments\n\n### Step 4: Verify Output and Results\n\nCheck the stdout\u002Fstderr from `run_shell` to:\n- Confirm execution succeeded (exit code 0)\n- Inspect printed output or results\n- Identify any new errors (different from sandbox errors)\n\nIf the script writes output files, use `read_file` to retrieve results.\n\n### Step 5: Clean Up (Optional)\n\nRemove temporary script files if they won't be reused:\n\n```python\nrun_shell(command=\"rm script.py\")\n```\n\n## Complete Example\n\n**Scenario:** `execute_code_sandbox` failed twice while trying to process data.\n\n**Fallback execution:**\n\n```python\n# Step 1: Write the processing script\nwrite_file(\n    path=\"process_data.py\",\n    content=\"\"\"\nimport pandas as pd\nimport json\n\ndef process():\n    data = [1, 2, 3, 4, 5]\n    result = {\"sum\": sum(data), \"count\": len(data)}\n    print(json.dumps(result))\n    \n    # Also save to file for reliability\n    with open(\"result.json\", \"w\") as f:\n        json.dump(result, f)\n\nif __name__ == \"__main__\":\n    process()\n\"\"\"\n)\n\n# Step 2: Execute via shell\noutput = run_shell(command=\"python3 process_data.py\")\n\n# Step 3: Read results from file\nresults = read_file(file_path=\"result.json\", filetype=\"json\")\n```\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| `python3: command not found` | Try `python` instead, or check available interpreters with `which python` |\n| Permission denied | Ensure the working directory is writable; `write_file` creates files in workspace by default |\n| Module not found | Install dependencies via `run_shell(command=\"pip install package_name\")` before execution |\n| Script hangs | Increase timeout parameter in `run_shell` |\n| Output too long | Redirect output to file within the script and read it separately |\n\n## Best Practices\n\n1. **Always include error handling** in scripts to capture failures gracefully\n2. **Write results to files** in addition to printing, for reliable retrieval\n3. **Use descriptive filenames** to avoid conflicts (e.g., `task_specific_script.py`)\n4. **Keep scripts self-contained** - avoid dependencies on sandbox environment variables\n5. **Log execution details** for debugging: `print(f\"Step X complete: {value}\")`\n\n## When NOT to Use This Fallback\n\n- When sandbox isolation is required for security\n- When the task explicitly requires `execute_code_sandbox`\n- When `execute_code_sandbox` succeeds consistently (no need to add complexity)\n- When working with sensitive data that shouldn't persist to disk",{"name":5,"description":7},"main","6b84b0689ca0d9e7b1e4061188ff6b60758e0f8a","openspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fcode-execution-fallback-e81068",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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add HKUDS\u002FAgentPilot --skill code-execution-fallback-e81068",{"tool":54,"command":55},"bunx","bunx skills add HKUDS\u002FAgentPilot --skill code-execution-fallback-e81068",{"tool":57,"command":58},"pnpm","pnpm dlx skills add HKUDS\u002FAgentPilot --skill code-execution-fallback-e81068","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fcode-execution-fallback-e81068\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},".skill_id","OTHER","其他",44,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fcode-execution-fallback-e81068\u002F.skill_id",[69,89,108,133,156,178],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":35},"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",[],[71,76,77,78,79,80,81,82,83,84,85,86,87,88],"prepare","requests","with","missing","installation","rsi","up","use","user","work","SET","run","experiments",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":35},"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",[],[91,96,97,98,99,100,101,102,103,104,105,106,107],"memory","review","auto","openspace","changes","facts","detect","entries","local","conflicts","stale","duplicates",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":119,"publishedAt":35},"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",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[120,121,122,99,123,124,125,126,127,128,129,130,131,132],"skill discovery","discovery","reusable","step by step","tokens","packages","help","cloud","reliability","capabilities","browse","search","Tools",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":35},"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",[139],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},[141,142,143,99,144,145,146,147,148,122,98,83,149,150,151,34,152,153,154,155],"delegate","task","delegate task","time","improve","desktop automation","worker","community","autonomous","tool","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":35},"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,164,165,166,167,168,169,170,171,29,172,173,174,175,34,176,177],"write special chars ts check","write","check","type","files","filters","only","template","file","typescript","output","Existing","type-checking","errors","script",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":35},"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",[],[185,186,164,78,34,177,187,188,189,190,191,170,171,192,193,29],"write special chars readback","readback","helper","post","via","scripts","read","verification","cleanup"]