[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KJ4QK9Y71M29PS71A07RGR":3,"skill-same:01M6KJ4QK9Y71M29PS71A07RGR":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6KJ4QK9Y71M29PS71A07RGR","fallback-code-execution",null,"Fallback workflow for running code via file write and shell when sandbox execution fails","AG064\u002FOpenSpace","AG064","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184930299?v=4","01M6KHVFG7TB73NHX3RDYSTMH2","01M6KHVFMM7XA2PZA9Z83PHS3V",0,"MIT","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Ffallback-code-execution\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34],"code","execution","fallback","code execution","fallback code execution","sandbox","workflow","file","shell","write","via","for","2026-11-10 10:12:30",false,"---\nname: fallback-code-execution\ndescription: Fallback workflow for running code via file write and shell when sandbox execution fails\n---\n\n# Fallback Code Execution Workflow\n\n## Overview\n\nThis skill defines a robust workaround for executing code (specifically Python) when the primary `execute_code_sandbox` tool fails repeatedly with unknown or transient errors. Instead of continuing to retry the failing tool, the agent switches to a manual file-write and shell-execution pattern.\n\n## Trigger Conditions\n\nActivate this workflow when:\n1.  `execute_code_sandbox` fails **2 or more times** consecutively for the same logic.\n2.  Error messages are generic, unknown, or indicate environment issues rather than syntax errors.\n3.  The code logic itself is verified correct but the execution environment is unstable.\n\n## Procedure\n\n### Step 1: Write Script to File\n\nUse the `write_file` tool to save the Python script to a specific path in the workspace.\n\n- **Path:** Choose a descriptive name ending in `.py` (e.g., `scripts\u002Fgenerate_report.py`).\n- **Content:** Ensure the script includes necessary error handling and print statements for debugging.\n- **Dependencies:** If the script requires external libraries, ensure a `requirements.txt` is updated or installed via shell beforehand.\n\n**Example:**\n```yaml\ntool: write_file\npath: workspace\u002Fscripts\u002Fprocess_data.py\ncontent: |\n  import sys\n  # ... script logic ...\n  print(\"Success\")\n```\n\n### Step 2: Execute via Shell\n\nUse the `run_shell` tool to execute the script using the system Python interpreter.\n\n- **Command:** `python3 \u003Cpath_to_script>` or `python \u003Cpath_to_script>`.\n- **Working Directory:** Ensure the shell command runs from the workspace root or the directory containing the script.\n- **Capture Output:** Store stdout and stderr for verification.\n\n**Example:**\n```yaml\ntool: run_shell\ncommand: python3 scripts\u002Fprocess_data.py\n```\n\n### Step 3: Verify Execution\n\n1.  **Check Exit Code:** Ensure the shell command returned exit code `0`.\n2.  **Check Output:** Verify expected files were created or expected stdout messages appeared.\n3.  **Handle Errors:** If the shell execution fails, inspect the stderr output. This often provides more detailed tracebacks than the sandbox tool.\n\n## Best Practices\n\n- **Absolute Paths:** When writing scripts that access files, use absolute paths or resolve paths relative to `__file__` to avoid working directory issues.\n- **Permissions:** Ensure the workspace directory allows file creation and execution.\n- **Cleanup:** Optionally remove temporary scripts after successful execution if cleanliness is required.\n- **Logging:** Add explicit `print()` statements in the Python script to log progress, as shell output capture is sometimes more reliable than sandbox return values.\n\n## Example Scenario\n\n**Problem:** `execute_code_sandbox` times out while generating a PDF.\n**Solution:**\n1.  Write `generate_pdf.py` to `workspace\u002Fscripts\u002F`.\n2.  Run `python3 workspace\u002Fscripts\u002Fgenerate_pdf.py` via `run_shell`.\n3.  Confirm `output.pdf` exists in the workspace.","# Fallback Code Execution Workflow\n\n## Overview\n\nThis skill defines a robust workaround for executing code (specifically Python) when the primary `execute_code_sandbox` tool fails repeatedly with unknown or transient errors. Instead of continuing to retry the failing tool, the agent switches to a manual file-write and shell-execution pattern.\n\n## Trigger Conditions\n\nActivate this workflow when:\n1.  `execute_code_sandbox` fails **2 or more times** consecutively for the same logic.\n2.  Error messages are generic, unknown, or indicate environment issues rather than syntax errors.\n3.  The code logic itself is verified correct but the execution environment is unstable.\n\n## Procedure\n\n### Step 1: Write Script to File\n\nUse the `write_file` tool to save the Python script to a specific path in the workspace.\n\n- **Path:** Choose a descriptive name ending in `.py` (e.g., `scripts\u002Fgenerate_report.py`).\n- **Content:** Ensure the script includes necessary error handling and print statements for debugging.\n- **Dependencies:** If the script requires external libraries, ensure a `requirements.txt` is updated or installed via shell beforehand.\n\n**Example:**\n```yaml\ntool: write_file\npath: workspace\u002Fscripts\u002Fprocess_data.py\ncontent: |\n  import sys\n  # ... script logic ...\n  print(\"Success\")\n```\n\n### Step 2: Execute via Shell\n\nUse the `run_shell` tool to execute the script using the system Python interpreter.\n\n- **Command:** `python3 \u003Cpath_to_script>` or `python \u003Cpath_to_script>`.\n- **Working Directory:** Ensure the shell command runs from the workspace root or the directory containing the script.\n- **Capture Output:** Store stdout and stderr for verification.\n\n**Example:**\n```yaml\ntool: run_shell\ncommand: python3 scripts\u002Fprocess_data.py\n```\n\n### Step 3: Verify Execution\n\n1.  **Check Exit Code:** Ensure the shell command returned exit code `0`.\n2.  **Check Output:** Verify expected files were created or expected stdout messages appeared.\n3.  **Handle Errors:** If the shell execution fails, inspect the stderr output. This often provides more detailed tracebacks than the sandbox tool.\n\n## Best Practices\n\n- **Absolute Paths:** When writing scripts that access files, use absolute paths or resolve paths relative to `__file__` to avoid working directory issues.\n- **Permissions:** Ensure the workspace directory allows file creation and execution.\n- **Cleanup:** Optionally remove temporary scripts after successful execution if cleanliness is required.\n- **Logging:** Add explicit `print()` statements in the Python script to log progress, as shell output capture is sometimes more reliable than sandbox return values.\n\n## Example Scenario\n\n**Problem:** `execute_code_sandbox` times out while generating a PDF.\n**Solution:**\n1.  Write `generate_pdf.py` to `workspace\u002Fscripts\u002F`.\n2.  Run `python3 workspace\u002Fscripts\u002Fgenerate_pdf.py` via `run_shell`.\n3.  Confirm `output.pdf` exists in the workspace.",{"name":5,"description":7},"main","ff671ef61ed6587c49bd54c81cdc751c0b99e363","gdpval_bench\u002Fskills\u002Ffallback-code-execution","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace","https:\u002F\u002Fgithub.com\u002FAG064","AG064, E.Mi.\r\n\r\nA person who thinks all the time, yet all they have to think about is nothing. I want to improve the world and work on open source projects","2026-10-08 06:53:48",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add AG064\u002FOpenSpace --skill fallback-code-execution",{"tool":53,"command":54},"bunx","bunx skills add AG064\u002FOpenSpace --skill fallback-code-execution",{"tool":56,"command":57},"pnpm","pnpm dlx skills add AG064\u002FOpenSpace --skill fallback-code-execution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Ffallback-code-execution\u002FSKILL.md",true,[61],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},".skill_id","OTHER","其他",37,"https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Ffallback-code-execution\u002F.skill_id",[68,89,105,113,141,157],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":35},"01M6KKMPWA0B5SCCH766F8M5EA","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\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[75,76,32,77,78,79,34,80,81,82,83,84,85,86,30,87,88],"write special chars ts check","check","filters","Existing","type-checking","errors","script","output","type","files","only","template","python","typescript",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":35},"01M6KKMJXVBNVEY3TRK055F4A7","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\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[96,97,32,86,98,99,30,87,100,101,33,102,103,34,81,104],"readback","write special chars readback","cleanup","read","scripts","verification","post","helper","with",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":35},"01M6KKMEGX9M9NC105J0W3Q5B9","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\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[32,112,87,34,33,86,31,30,81],"write special chars heredoc",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":122,"publishedAt":35},"01M6KKM8EJ2AATVHZBNB916WT0","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\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000033","数据分析师",[123,124,125,126,88,127,128,129,130,131,34,132,133,134,135,136,137,138,139,140],"reference","worldmonitor","worldmonitor reference","dashboard","css","architecture","extracting","hierarchy","source","layer","panel","patterns","edge functions","integrations","open","api","data","scheduler",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":35},"01M6KKM39PHYK627F19GE2B9XN","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[148,149,150,151,34,152,104,153,154,155,156],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":35},"01M6KKKY7T2P61Y0JH54CDEJKQ","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[164,165,166,167,168,169,30,170,171,172],"directory","verify","structure","verify directory structure","access","first","issues","diagnose","file access"]