[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KJTWMQFH0V6JF6H2VBSFDR":3,"skill-same:01M6KJTWMQFH0V6JF6H2VBSFDR":60},{"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":17,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M6KJTWMQFH0V6JF6H2VBSFDR","python-execution-fallback",null,"Four-step recovery workflow for code execution failures when inline Python 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\u002Fpython-execution-fallback\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27],"python","execution","fallback","python execution fallback","workflow","code","recovery","code execution","for","inline","2026-11-10 10:12:30",false,"---\nname: python-execution-fallback\ndescription: Four-step recovery workflow for code execution failures when inline Python fails\n---\n\n# Python Execution Fallback Workflow\n\nThis skill provides a systematic debugging approach when inline Python code execution fails, particularly in heredoc or shell_agent contexts.\n\n## Pattern Overview\n\nWhen Python code execution fails, follow this recovery workflow:\n\n1. **Attempt inline execution first** - Try running Python code directly\n2. **Write script to file on failure** - Persist the code to a `.py` file\n3. **Execute the file** - Run the saved script via shell\n4. **Validate output** - Verify results are correct and complete\n\n## When to Use\n\nApply this pattern when:\n- Inline Python execution fails with syntax or runtime errors\n- Heredoc-based code execution encounters parsing issues\n- Working with complex multi-line scripts that need debugging\n- Need systematic approach to isolate execution failures\n- Spreadsheet\u002Fdata generation tasks fail in inline mode\n\n## Step-by-Step Instructions\n\n### Step 1: Attempt Inline Execution\n\nTry executing Python code inline first (using execute_code_sandbox or similar):\n\n```python\n# Example: Attempt inline execution\nimport pandas as pd\nimport openpyxl\n\ndf = pd.read_excel(\"input.xlsx\")\n# Process data...\ndf.to_excel(\"output.xlsx\", index=False)\n```\n\nIf this succeeds, proceed. If it fails, move to Step 2.\n\n### Step 2: Write Script to File (On Failure)\n\nWhen inline execution fails, write the complete script to a persistent file:\n\n```python\n# Capture the script content\nscript_content = '''\nimport pandas as pd\nimport openpyxl\nimport sys\n\ntry:\n    # Your original code here\n    df = pd.read_excel(\"input.xlsx\")\n    \n    # Processing logic\n    result_df = df.groupby(\"category\").sum()\n    \n    # Output\n    result_df.to_excel(\"output.xlsx\", index=False)\n    print(\"SUCCESS: File generated\")\n    \nexcept Exception as e:\n    print(f\"ERROR: {e}\", file=sys.stderr)\n    sys.exit(1)\n'''\n\n# Write to file\nwith open(\"script.py\", \"w\") as f:\n    f.write(script_content)\n\nprint(\"Script written to script.py\")\n```\n\n### Step 3: Execute the File\n\nRun the saved script using shell execution:\n\n```bash\npython script.py\n```\n\nOr with error capture:\n\n```bash\npython script.py 2>&1 | tee execution.log\n```\n\nThis approach:\n- Avoids heredoc parsing issues\n- Provides clearer error messages\n- Allows script inspection and modification\n- Enables re-execution without rewriting\n\n### Step 4: Validate Output\n\nVerify the results are correct:\n\n```python\n# Validation script\nimport pandas as pd\nimport os\n\n# Check file exists\nif os.path.exists(\"output.xlsx\"):\n    df = pd.read_excel(\"output.xlsx\")\n    print(f\"Rows: {len(df)}, Columns: {len(df.columns)}\")\n    print(df.head())\n    print(\"VALIDATION: PASSED\")\nelse:\n    print(\"VALIDATION: FAILED - Output file missing\")\n```\n\n## Code Example: Complete Workflow\n\n```python\n# Full fallback workflow example\ndef generate_spreadsheet_fallback(data, output_path):\n    \"\"\"Generate spreadsheet with fallback workflow\"\"\"\n    \n    # Step 1: Try inline\n    inline_script = f'''\nimport pandas as pd\ndata = {data}\ndf = pd.DataFrame(data)\ndf.to_excel(\"{output_path}\", index=False)\n'''\n    \n    try:\n        # Attempt inline execution\n        result = execute_code_sandbox(code=inline_script)\n        if \"error\" not in result.lower():\n            return \"SUCCESS_INLINE\"\n    except Exception as e:\n        pass\n    \n    # Step 2: Write to file\n    file_script = f'''\nimport pandas as pd\nimport sys\n\ntry:\n    data = {data}\n    df = pd.DataFrame(data)\n    df.to_excel(\"{output_path}\", index=False)\n    print(\"SUCCESS\")\nexcept Exception as e:\n    print(f\"ERROR: {{e}}\", file=sys.stderr)\n    sys.exit(1)\n'''\n    \n    with open(\"generate.py\", \"w\") as f:\n        f.write(file_script)\n    \n    # Step 3: Execute file\n    shell_result = run_shell(command=\"python generate.py\")\n    \n    # Step 4: Validate\n    if os.path.exists(output_path):\n        return \"SUCCESS_FILE\"\n    else:\n        return \"FAILED\"\n```\n\n## Best Practices\n\n1. **Include error handling** in file-based scripts (try\u002Fexcept with sys.stderr)\n2. **Add success indicators** (print statements) to confirm execution\n3. **Preserve original logic** when converting from inline to file\n4. **Check return codes** when executing scripts via shell\n5. **Clean up temporary files** after successful validation\n6. **Log both stdout and stderr** for debugging\n\n## Common Failure Scenarios\n\nThis pattern helps resolve:\n- Heredoc string escaping issues\n- Multi-line code formatting problems\n- Import path resolution failures\n- Environment variable access issues\n- Complex indentation in inline code\n\n## Related Patterns\n\n- Combine with `retry-with-modification` for iterative debugging\n- Use alongside `output-validation-check` for result verification\n- Pair with `error-log-analysis` for root cause identification","# Python Execution Fallback Workflow\n\nThis skill provides a systematic debugging approach when inline Python code execution fails, particularly in heredoc or shell_agent contexts.\n\n## Pattern Overview\n\nWhen Python code execution fails, follow this recovery workflow:\n\n1. **Attempt inline execution first** - Try running Python code directly\n2. **Write script to file on failure** - Persist the code to a `.py` file\n3. **Execute the file** - Run the saved script via shell\n4. **Validate output** - Verify results are correct and complete\n\n## When to Use\n\nApply this pattern when:\n- Inline Python execution fails with syntax or runtime errors\n- Heredoc-based code execution encounters parsing issues\n- Working with complex multi-line scripts that need debugging\n- Need systematic approach to isolate execution failures\n- Spreadsheet\u002Fdata generation tasks fail in inline mode\n\n## Step-by-Step Instructions\n\n### Step 1: Attempt Inline Execution\n\nTry executing Python code inline first (using execute_code_sandbox or similar):\n\n```python\n# Example: Attempt inline execution\nimport pandas as pd\nimport openpyxl\n\ndf = pd.read_excel(\"input.xlsx\")\n# Process data...\ndf.to_excel(\"output.xlsx\", index=False)\n```\n\nIf this succeeds, proceed. If it fails, move to Step 2.\n\n### Step 2: Write Script to File (On Failure)\n\nWhen inline execution fails, write the complete script to a persistent file:\n\n```python\n# Capture the script content\nscript_content = '''\nimport pandas as pd\nimport openpyxl\nimport sys\n\ntry:\n    # Your original code here\n    df = pd.read_excel(\"input.xlsx\")\n    \n    # Processing logic\n    result_df = df.groupby(\"category\").sum()\n    \n    # Output\n    result_df.to_excel(\"output.xlsx\", index=False)\n    print(\"SUCCESS: File generated\")\n    \nexcept Exception as e:\n    print(f\"ERROR: {e}\", file=sys.stderr)\n    sys.exit(1)\n'''\n\n# Write to file\nwith open(\"script.py\", \"w\") as f:\n    f.write(script_content)\n\nprint(\"Script written to script.py\")\n```\n\n### Step 3: Execute the File\n\nRun the saved script using shell execution:\n\n```bash\npython script.py\n```\n\nOr with error capture:\n\n```bash\npython script.py 2>&1 | tee execution.log\n```\n\nThis approach:\n- Avoids heredoc parsing issues\n- Provides clearer error messages\n- Allows script inspection and modification\n- Enables re-execution without rewriting\n\n### Step 4: Validate Output\n\nVerify the results are correct:\n\n```python\n# Validation script\nimport pandas as pd\nimport os\n\n# Check file exists\nif os.path.exists(\"output.xlsx\"):\n    df = pd.read_excel(\"output.xlsx\")\n    print(f\"Rows: {len(df)}, Columns: {len(df.columns)}\")\n    print(df.head())\n    print(\"VALIDATION: PASSED\")\nelse:\n    print(\"VALIDATION: FAILED - Output file missing\")\n```\n\n## Code Example: Complete Workflow\n\n```python\n# Full fallback workflow example\ndef generate_spreadsheet_fallback(data, output_path):\n    \"\"\"Generate spreadsheet with fallback workflow\"\"\"\n    \n    # Step 1: Try inline\n    inline_script = f'''\nimport pandas as pd\ndata = {data}\ndf = pd.DataFrame(data)\ndf.to_excel(\"{output_path}\", index=False)\n'''\n    \n    try:\n        # Attempt inline execution\n        result = execute_code_sandbox(code=inline_script)\n        if \"error\" not in result.lower():\n            return \"SUCCESS_INLINE\"\n    except Exception as e:\n        pass\n    \n    # Step 2: Write to file\n    file_script = f'''\nimport pandas as pd\nimport sys\n\ntry:\n    data = {data}\n    df = pd.DataFrame(data)\n    df.to_excel(\"{output_path}\", index=False)\n    print(\"SUCCESS\")\nexcept Exception as e:\n    print(f\"ERROR: {{e}}\", file=sys.stderr)\n    sys.exit(1)\n'''\n    \n    with open(\"generate.py\", \"w\") as f:\n        f.write(file_script)\n    \n    # Step 3: Execute file\n    shell_result = run_shell(command=\"python generate.py\")\n    \n    # Step 4: Validate\n    if os.path.exists(output_path):\n        return \"SUCCESS_FILE\"\n    else:\n        return \"FAILED\"\n```\n\n## Best Practices\n\n1. **Include error handling** in file-based scripts (try\u002Fexcept with sys.stderr)\n2. **Add success indicators** (print statements) to confirm execution\n3. **Preserve original logic** when converting from inline to file\n4. **Check return codes** when executing scripts via shell\n5. **Clean up temporary files** after successful validation\n6. **Log both stdout and stderr** for debugging\n\n## Common Failure Scenarios\n\nThis pattern helps resolve:\n- Heredoc string escaping issues\n- Multi-line code formatting problems\n- Import path resolution failures\n- Environment variable access issues\n- Complex indentation in inline code\n\n## Related Patterns\n\n- Combine with `retry-with-modification` for iterative debugging\n- Use alongside `output-validation-check` for result verification\n- Pair with `error-log-analysis` for root cause identification",{"name":5,"description":7},"main","ff671ef61ed6587c49bd54c81cdc751c0b99e363","gdpval_bench\u002Fskills\u002Fpython-execution-fallback","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":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add AG064\u002FOpenSpace --skill python-execution-fallback",{"tool":46,"command":47},"bunx","bunx skills add AG064\u002FOpenSpace --skill python-execution-fallback",{"tool":49,"command":50},"pnpm","pnpm dlx skills add AG064\u002FOpenSpace --skill python-execution-fallback","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fpython-execution-fallback\u002FSKILL.md",true,[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},".skill_id","OTHER","其他",39,"https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fpython-execution-fallback\u002F.skill_id",[61,83,100,109,139,155],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":28},"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",[],[68,69,70,71,72,73,26,74,75,76,77,78,79,80,81,18,82],"write special chars ts check","check","write","filters","Existing","type-checking","errors","script","output","type","files","only","template","file","typescript",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":28},"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",[],[90,91,70,80,92,93,81,18,94,95,96,97,98,26,75,99],"readback","write special chars readback","cleanup","read","scripts","verification","via","post","helper","with",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":28},"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",[],[70,107,18,26,96,80,108,81,75],"write special chars heredoc","shell",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":28},"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",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[121,122,123,124,82,125,126,127,128,129,26,130,131,132,133,134,135,136,137,138],"reference","worldmonitor","worldmonitor reference","dashboard","css","architecture","extracting","hierarchy","source","layer","panel","patterns","edge functions","integrations","open","api","data","scheduler",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":28},"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",[],[146,147,148,149,26,150,99,151,152,153,154],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":28},"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",[],[162,163,164,165,166,167,81,168,169,170],"directory","verify","structure","verify directory structure","access","first","issues","diagnose","file access"]