Troubleshoot file access failures caused by commands running in the wrong folder. Set the working directory explicitly before file operations, check directory paths, and locate files when relative paths resolve differently across tools.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Resolve file access failures by changing to the correct working directory before command execution
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Many 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.
File operations fail with errors like:
These failures often occur even when files are present in the workspace—the working directory context is simply wrong.
Always explicitly set the working directory before file operations by prepending cd to your shell commands.
cd /path/to/target/directory && your-command-here
run_shellrun_shell(command="cd /workspace/project && cat config.json")
cd /workspace/project && ls -la && cat README.md && python script.py
cd /workspace/project 2>/dev/null && cat file.txt || echo "Directory not found"
Use this pattern when:
read_file fails to locate an existing fileexecute_code_sandbox can't find referenced filesUse absolute paths when possible
cd /workspace/project/src && python main.py
Combine related operations to avoid repeated cd calls
cd /workspace/project && ./build.sh && ./test.sh
Verify directory exists before operations
[ -d /workspace/project ] && cd /workspace/project && ls
For scripts, set working directory at the start
#!/bin/bash
cd "$(dirname "$0")" || exit 1
# Rest of script runs from script's directory
| Issue | Wrong Approach | Correct Approach |
|---|---|---|
| Relative paths | cat config.json | cd /workspace && cat config.json |
| Assumed cwd | python script.py | cd /workspace && python script.py |
| Multiple dirs | cd dir1; cd dir2; cmd | cd dir1/dir2 && cmd |
If cd also fails:
pwd to check current directoryfind or ls -R to locate filesls -la /path/to/checkpwd && find /workspace -name "target_file.txt" 2>/dev/null
This pattern is especially valuable when tools like execute_code_sandbox or read_file fail but run_shell with explicit directory context succeeds.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Prepare audio stems, the separate parts of a track, for mixing by matching their durations with silence, loops, or crossfades. Verify each generated and processed file before moving to the next production step.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Produce audio in separate stems, meaning individual instrument tracks, and verify each output as you go. Align track lengths with silence, loops, or crossfades, then apply effects, mix a master, and package the files.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build serverless endpoints that relay external API requests for a dashboard while keeping API keys on the server. Includes Vercel examples for input checks, caching, cross-origin access, and consistent JSON responses.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.