[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XC4P8EK7EVT93RHXZH1ZX5":3,"skill-same:01M6XC4P8EK7EVT93RHXZH1ZX5":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M6XC4P8EK7EVT93RHXZH1ZX5","working-directory-resolution",null,"Resolve file access failures by changing to the correct working directory before command execution","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fworking-directory-resolution\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26],"directory","resolution","working directory resolution","file access","file","execution","access","correct","command","2026-11-10 10:12:30",false,"---\nname: working-directory-resolution\ndescription: Resolve file access failures by changing to the correct working directory before command execution\n---\n\n# Working Directory Resolution Pattern\n\nMany file operation failures occur because the tool's current working directory doesn't match where the target files are located. This skill provides a reliable pattern for resolving such issues.\n\n## Problem Symptoms\n\nFile operations fail with errors like:\n- \"File not found\" or \"No such file or directory\"\n- \"Permission denied\" (when path is actually relative)\n- Tools returning empty results for files that should exist\n\nThese failures often occur even when files are present in the workspace—the working directory context is simply wrong.\n\n## Solution\n\n**Always explicitly set the working directory before file operations** by prepending `cd` to your shell commands.\n\n## Implementation Pattern\n\n### Basic Syntax\n```bash\ncd \u002Fpath\u002Fto\u002Ftarget\u002Fdirectory && your-command-here\n```\n\n### With `run_shell`\n```bash\nrun_shell(command=\"cd \u002Fworkspace\u002Fproject && cat config.json\")\n```\n\n### Multiple Operations in Same Directory\n```bash\ncd \u002Fworkspace\u002Fproject && ls -la && cat README.md && python script.py\n```\n\n### Conditional Directory Change\n```bash\ncd \u002Fworkspace\u002Fproject 2>\u002Fdev\u002Fnull && cat file.txt || echo \"Directory not found\"\n```\n\n## When to Apply\n\nUse this pattern when:\n- `read_file` fails to locate an existing file\n- `execute_code_sandbox` can't find referenced files\n- Shell commands report missing files that should exist\n- File paths work in some contexts but not others\n- You're unsure of the tool's current working directory\n\n## Best Practices\n\n1. **Use absolute paths when possible**\n   ```bash\n   cd \u002Fworkspace\u002Fproject\u002Fsrc && python main.py\n   ```\n\n2. **Combine related operations** to avoid repeated `cd` calls\n   ```bash\n   cd \u002Fworkspace\u002Fproject && .\u002Fbuild.sh && .\u002Ftest.sh\n   ```\n\n3. **Verify directory exists before operations**\n   ```bash\n   [ -d \u002Fworkspace\u002Fproject ] && cd \u002Fworkspace\u002Fproject && ls\n   ```\n\n4. **For scripts, set working directory at the start**\n   ```bash\n   #!\u002Fbin\u002Fbash\n   cd \"$(dirname \"$0\")\" || exit 1\n   # Rest of script runs from script's directory\n   ```\n\n## Common Pitfalls\n\n| Issue | Wrong Approach | Correct Approach |\n|-------|---------------|------------------|\n| Relative paths | `cat config.json` | `cd \u002Fworkspace && cat config.json` |\n| Assumed cwd | `python script.py` | `cd \u002Fworkspace && python script.py` |\n| Multiple dirs | `cd dir1; cd dir2; cmd` | `cd dir1\u002Fdir2 && cmd` |\n\n## Fallback Strategy\n\nIf `cd` also fails:\n1. Use `pwd` to check current directory\n2. Use `find` or `ls -R` to locate files\n3. Verify the path structure with `ls -la \u002Fpath\u002Fto\u002Fcheck`\n\n```bash\npwd && find \u002Fworkspace -name \"target_file.txt\" 2>\u002Fdev\u002Fnull\n```\n\n---\n\nThis pattern is especially valuable when tools like `execute_code_sandbox` or `read_file` fail but `run_shell` with explicit directory context succeeds.","# Working Directory Resolution Pattern\n\nMany file operation failures occur because the tool's current working directory doesn't match where the target files are located. This skill provides a reliable pattern for resolving such issues.\n\n## Problem Symptoms\n\nFile operations fail with errors like:\n- \"File not found\" or \"No such file or directory\"\n- \"Permission denied\" (when path is actually relative)\n- Tools returning empty results for files that should exist\n\nThese failures often occur even when files are present in the workspace—the working directory context is simply wrong.\n\n## Solution\n\n**Always explicitly set the working directory before file operations** by prepending `cd` to your shell commands.\n\n## Implementation Pattern\n\n### Basic Syntax\n```bash\ncd \u002Fpath\u002Fto\u002Ftarget\u002Fdirectory && your-command-here\n```\n\n### With `run_shell`\n```bash\nrun_shell(command=\"cd \u002Fworkspace\u002Fproject && cat config.json\")\n```\n\n### Multiple Operations in Same Directory\n```bash\ncd \u002Fworkspace\u002Fproject && ls -la && cat README.md && python script.py\n```\n\n### Conditional Directory Change\n```bash\ncd \u002Fworkspace\u002Fproject 2>\u002Fdev\u002Fnull && cat file.txt || echo \"Directory not found\"\n```\n\n## When to Apply\n\nUse this pattern when:\n- `read_file` fails to locate an existing file\n- `execute_code_sandbox` can't find referenced files\n- Shell commands report missing files that should exist\n- File paths work in some contexts but not others\n- You're unsure of the tool's current working directory\n\n## Best Practices\n\n1. **Use absolute paths when possible**\n   ```bash\n   cd \u002Fworkspace\u002Fproject\u002Fsrc && python main.py\n   ```\n\n2. **Combine related operations** to avoid repeated `cd` calls\n   ```bash\n   cd \u002Fworkspace\u002Fproject && .\u002Fbuild.sh && .\u002Ftest.sh\n   ```\n\n3. **Verify directory exists before operations**\n   ```bash\n   [ -d \u002Fworkspace\u002Fproject ] && cd \u002Fworkspace\u002Fproject && ls\n   ```\n\n4. **For scripts, set working directory at the start**\n   ```bash\n   #!\u002Fbin\u002Fbash\n   cd \"$(dirname \"$0\")\" || exit 1\n   # Rest of script runs from script's directory\n   ```\n\n## Common Pitfalls\n\n| Issue | Wrong Approach | Correct Approach |\n|-------|---------------|------------------|\n| Relative paths | `cat config.json` | `cd \u002Fworkspace && cat config.json` |\n| Assumed cwd | `python script.py` | `cd \u002Fworkspace && python script.py` |\n| Multiple dirs | `cd dir1; cd dir2; cmd` | `cd dir1\u002Fdir2 && cmd` |\n\n## Fallback Strategy\n\nIf `cd` also fails:\n1. Use `pwd` to check current directory\n2. Use `find` or `ls -R` to locate files\n3. Verify the path structure with `ls -la \u002Fpath\u002Fto\u002Fcheck`\n\n```bash\npwd && find \u002Fworkspace -name \"target_file.txt\" 2>\u002Fdev\u002Fnull\n```\n\n---\n\nThis pattern is especially valuable when tools like `execute_code_sandbox` or `read_file` fail but `run_shell` with explicit directory context succeeds.",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fworking-directory-resolution","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill working-directory-resolution",{"tool":44,"command":45},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill working-directory-resolution",{"tool":47,"command":48},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill working-directory-resolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fworking-directory-resolution\u002FSKILL.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},".skill_id","OTHER","其他",42,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fworking-directory-resolution\u002F.skill_id",[59,83,100,109,139,155],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":27},"01M6XCCXD3NCM2YKR3WNGBASPC","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,22,82],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","files","only","template","python",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":27},"01M6XCCT7E3J922Q345PBGSHPN","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[90,91,67,22,92,82,93,94,95,96,97,81,98,99,71,74,76],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification","with",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":27},"01M6XCCMQX1R8B6FECWB3P63T7","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[107,67,71,108,76,94,81,22,82,74],"write special chars heredoc","shell",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":27},"01M6XCCG41M994JJEX6VN52PEP","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[121,122,123,124,125,69,126,127,128,129,130,74,131,132,133,134,135,136,137,138],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":27},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[146,147,148,149,74,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":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":27},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[18,162,163,164,24,165,22,166,167,21],"verify directory structure","structure","verify","first","issues","diagnose"]