[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HX5CDZVF7T49KPK2TMV6QP":3,"skill-same:01M6HX5CDZVF7T49KPK2TMV6QP":61},{"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":18,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6HX5CDZVF7T49KPK2TMV6QP","working-directory-resolution",null,"Resolve file access failures by changing to the correct working directory before command execution","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\u002Fworking-directory-resolution\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"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","6b84b0689ca0d9e7b1e4061188ff6b60758e0f8a","openspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fworking-directory-resolution",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add HKUDS\u002FAgentPilot --skill working-directory-resolution",{"tool":47,"command":48},"bunx","bunx skills add HKUDS\u002FAgentPilot --skill working-directory-resolution",{"tool":50,"command":51},"pnpm","pnpm dlx skills add HKUDS\u002FAgentPilot --skill working-directory-resolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fworking-directory-resolution\u002FSKILL.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},".skill_id","OTHER","其他",42,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fbenchmarks\u002Fgdpval\u002Fskills\u002Fworking-directory-resolution\u002F.skill_id",[62,82,101,126,150,172],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":28},"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",[],[64,69,70,71,72,73,74,75,76,77,78,79,80,81],"prepare","requests","with","missing","installation","rsi","up","use","user","work","SET","run","experiments",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":28},"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",[],[84,89,90,91,92,93,94,95,96,97,98,99,100],"memory","review","auto","openspace","changes","facts","detect","entries","local","conflicts","stale","duplicates",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":112,"publishedAt":28},"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",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[113,114,115,92,116,117,118,119,120,121,122,123,124,125],"skill discovery","discovery","reusable","step by step","tokens","packages","help","cloud","reliability","capabilities","browse","search","Tools",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":133,"publishedAt":28},"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",[132],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},[134,135,136,92,137,138,139,140,141,115,91,76,142,143,144,145,146,147,148,149],"delegate","task","delegate task","time","improve","desktop automation","worker","community","autonomous","tool","stack","for","share","tasks","automation","MCP",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":28},"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",[],[157,158,159,160,161,162,163,164,23,165,166,167,168,169,145,170,171],"write special chars ts check","write","check","type","files","filters","only","template","python","typescript","output","Existing","type-checking","errors","script",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":28},"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",[],[179,180,158,71,145,171,181,182,183,184,185,164,23,186,187,165],"write special chars readback","readback","helper","post","via","scripts","read","verification","cleanup"]