[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KJ4ZDHFHPMD8EWK2WKYY4T":3,"skill-same:01M6KJ4ZDHFHPMD8EWK2WKYY4T":63},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":13,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M6KJ4ZDHFHPMD8EWK2WKYY4T","fallback-file-ops",null,"Use run_shell as fallback when execute_code_sandbox or shell_agent fail on filesystem operations","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-file-ops\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30],"file","ops","fallback","fallback file ops","sandbox","run","code","shell","filesystem","execute","operations","use","as","2026-11-10 10:12:30",false,"---\nname: fallback-file-ops\ndescription: Use run_shell as fallback when execute_code_sandbox or shell_agent fail on filesystem operations\n---\n\n# Fallback File Operations\n\n## Purpose\n\nWhen `execute_code_sandbox` or `shell_agent` fail with 'unknown error' on filesystem operations, fall back to `run_shell` with explicit `mkdir` and file write commands. This hybrid approach is more reliable for creating complex project structures.\n\n## When to Apply\n\n- `execute_code_sandbox` returns 'unknown error' on file\u002Fdirectory creation\n- `shell_agent` fails to write files or create nested directories\n- You need to create complex project structures with multiple levels\n\n## Procedure\n\n### Step 1: Detect Tool Failure\n\n Monitor for these failure patterns:\n- Error message contains \"unknown error\"\n- File operations silently fail (file not created)\n- Directory creation returns success but directory doesn't exist\n\n### Step 2: Switch to run_shell\n\nWhen failures occur, immediately switch to `run_shell` for filesystem operations:\n\n```bash\n# Create directory structure explicitly\nrun_shell: mkdir -p \u002Fpath\u002Fto\u002Fnested\u002Fdirectory\n\n# Write files using shell redirection or echo\nrun_shell: echo \"content\" > \u002Fpath\u002Fto\u002Ffile.txt\n\n# Or use cat with heredoc for multi-line files\nrun_shell: cat > \u002Fpath\u002Fto\u002Ffile.txt \u003C\u003C 'EOF'\nline 1\nline 2\nEOF\n```\n\n### Step 3: Verify Creation\n\nAfter each operation, verify the file\u002Fdirectory was created:\n\n```bash\nrun_shell: ls -la \u002Fpath\u002Fto\u002Fcreated\u002Fitem\nrun_shell: test -f \u002Fpath\u002Fto\u002Ffile && echo \"File exists\"\nrun_shell: test -d \u002Fpath\u002Fto\u002Fdir && echo \"Directory exists\"\n```\n\n### Step 4: Continue with Hybrid Approach\n\n- Use `run_shell` for all filesystem operations (mkdir, write, copy, move)\n- Continue using `execute_code_sandbox` or `shell_agent` for code execution, compilation, or other non-filesystem tasks\n- Document which tool handles which operation for clarity\n\n## Example: Creating Project Structure\n\n```yaml\n# Failed attempt with execute_code_sandbox\nexecute_code_sandbox: create directory src\u002Fcomponents\n\n# Fallback with run_shell\nrun_shell: mkdir -p src\u002Fcomponents\nrun_shell: mkdir -p src\u002Futils\nrun_shell: mkdir -p tests\u002Funit\nrun_shell: echo \"\u002F\u002F Component file\" > src\u002Fcomponents\u002FButton.tsx\nrun_shell: echo \"\u002F\u002F Utility file\" > src\u002Futils\u002Fhelpers.ts\n```\n\n## Best Practices\n\n1. **Be explicit**: Always use full paths or confirm working directory\n2. **Create parent directories**: Use `mkdir -p` for nested structures\n3. **Verify before proceeding**: Check files exist before dependent operations\n4. **Log tool switches**: Note when you fall back to run_shell for debugging\n5. **Batch operations**: Group related file operations in consecutive run_shell calls\n\n## Common Pitfalls\n\n- Don't assume filesystem state after tool failure\n- Don't mix tools for the same file operation (pick one and stick with it)\n- Don't skip verification steps when using fallback","# Fallback File Operations\n\n## Purpose\n\nWhen `execute_code_sandbox` or `shell_agent` fail with 'unknown error' on filesystem operations, fall back to `run_shell` with explicit `mkdir` and file write commands. This hybrid approach is more reliable for creating complex project structures.\n\n## When to Apply\n\n- `execute_code_sandbox` returns 'unknown error' on file\u002Fdirectory creation\n- `shell_agent` fails to write files or create nested directories\n- You need to create complex project structures with multiple levels\n\n## Procedure\n\n### Step 1: Detect Tool Failure\n\n Monitor for these failure patterns:\n- Error message contains \"unknown error\"\n- File operations silently fail (file not created)\n- Directory creation returns success but directory doesn't exist\n\n### Step 2: Switch to run_shell\n\nWhen failures occur, immediately switch to `run_shell` for filesystem operations:\n\n```bash\n# Create directory structure explicitly\nrun_shell: mkdir -p \u002Fpath\u002Fto\u002Fnested\u002Fdirectory\n\n# Write files using shell redirection or echo\nrun_shell: echo \"content\" > \u002Fpath\u002Fto\u002Ffile.txt\n\n# Or use cat with heredoc for multi-line files\nrun_shell: cat > \u002Fpath\u002Fto\u002Ffile.txt \u003C\u003C 'EOF'\nline 1\nline 2\nEOF\n```\n\n### Step 3: Verify Creation\n\nAfter each operation, verify the file\u002Fdirectory was created:\n\n```bash\nrun_shell: ls -la \u002Fpath\u002Fto\u002Fcreated\u002Fitem\nrun_shell: test -f \u002Fpath\u002Fto\u002Ffile && echo \"File exists\"\nrun_shell: test -d \u002Fpath\u002Fto\u002Fdir && echo \"Directory exists\"\n```\n\n### Step 4: Continue with Hybrid Approach\n\n- Use `run_shell` for all filesystem operations (mkdir, write, copy, move)\n- Continue using `execute_code_sandbox` or `shell_agent` for code execution, compilation, or other non-filesystem tasks\n- Document which tool handles which operation for clarity\n\n## Example: Creating Project Structure\n\n```yaml\n# Failed attempt with execute_code_sandbox\nexecute_code_sandbox: create directory src\u002Fcomponents\n\n# Fallback with run_shell\nrun_shell: mkdir -p src\u002Fcomponents\nrun_shell: mkdir -p src\u002Futils\nrun_shell: mkdir -p tests\u002Funit\nrun_shell: echo \"\u002F\u002F Component file\" > src\u002Fcomponents\u002FButton.tsx\nrun_shell: echo \"\u002F\u002F Utility file\" > src\u002Futils\u002Fhelpers.ts\n```\n\n## Best Practices\n\n1. **Be explicit**: Always use full paths or confirm working directory\n2. **Create parent directories**: Use `mkdir -p` for nested structures\n3. **Verify before proceeding**: Check files exist before dependent operations\n4. **Log tool switches**: Note when you fall back to run_shell for debugging\n5. **Batch operations**: Group related file operations in consecutive run_shell calls\n\n## Common Pitfalls\n\n- Don't assume filesystem state after tool failure\n- Don't mix tools for the same file operation (pick one and stick with it)\n- Don't skip verification steps when using fallback",{"name":5,"description":7},"main","ff671ef61ed6587c49bd54c81cdc751c0b99e363","gdpval_bench\u002Fskills\u002Ffallback-file-ops","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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add AG064\u002FOpenSpace --skill fallback-file-ops",{"tool":49,"command":50},"bunx","bunx skills add AG064\u002FOpenSpace --skill fallback-file-ops",{"tool":52,"command":53},"pnpm","pnpm dlx skills add AG064\u002FOpenSpace --skill fallback-file-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Ffallback-file-ops\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},".skill_id","OTHER","其他",31,"https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Ffallback-file-ops\u002F.skill_id",[64,87,104,112,142,158],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":31},"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",[],[71,72,73,74,75,76,77,78,79,80,81,82,83,84,18,85,86],"write special chars ts check","check","write","filters","Existing","type-checking","for","errors","script","output","type","files","only","template","python","typescript",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":31},"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",[],[94,95,73,84,96,97,18,85,98,99,100,101,102,77,79,103],"readback","write special chars readback","cleanup","read","scripts","verification","via","post","helper","with",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":31},"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",[],[73,111,85,77,100,84,25,18,79],"write special chars heredoc",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":123,"publishedAt":31},"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",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[124,125,126,127,86,128,129,130,131,132,77,133,134,135,136,137,138,139,140,141],"reference","worldmonitor","worldmonitor reference","dashboard","css","architecture","extracting","hierarchy","source","layer","panel","patterns","edge functions","integrations","open","api","data","scheduler",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":31},"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",[],[149,150,151,152,77,153,103,154,155,156,157],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":31},"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",[],[165,166,167,168,169,170,18,171,172,173],"directory","verify","structure","verify directory structure","access","first","issues","diagnose","file access"]