Skip to content
cccskills
FreePublished on GitHub

working-directory-resolution

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.

OriginalShow the original description

Resolve file access failures by changing to the correct working directory before command execution

See how to install

Good for

  • Troubleshooting missing-file errors for existing files
  • Running scripts from the intended project folder
  • Checking paths that behave differently across tools

Files included (2)

  • SKILL.md2.9 KB
  • .skill_id42 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Working Directory Resolution Pattern

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.

Problem Symptoms

File operations fail with errors like:

  • "File not found" or "No such file or directory"
  • "Permission denied" (when path is actually relative)
  • Tools returning empty results for files that should exist

These failures often occur even when files are present in the workspace—the working directory context is simply wrong.

Solution

Always explicitly set the working directory before file operations by prepending cd to your shell commands.

Implementation Pattern

Basic Syntax

cd /path/to/target/directory && your-command-here

With run_shell

run_shell(command="cd /workspace/project && cat config.json")

Multiple Operations in Same Directory

cd /workspace/project && ls -la && cat README.md && python script.py

Conditional Directory Change

cd /workspace/project 2>/dev/null && cat file.txt || echo "Directory not found"

When to Apply

Use this pattern when:

  • read_file fails to locate an existing file
  • execute_code_sandbox can't find referenced files
  • Shell commands report missing files that should exist
  • File paths work in some contexts but not others
  • You're unsure of the tool's current working directory

Best Practices

  1. Use absolute paths when possible

    cd /workspace/project/src && python main.py
    
  2. Combine related operations to avoid repeated cd calls

    cd /workspace/project && ./build.sh && ./test.sh
    
  3. Verify directory exists before operations

    [ -d /workspace/project ] && cd /workspace/project && ls
    
  4. For scripts, set working directory at the start

    #!/bin/bash
    cd "$(dirname "$0")" || exit 1
    # Rest of script runs from script's directory
    

Common Pitfalls

IssueWrong ApproachCorrect Approach
Relative pathscat config.jsoncd /workspace && cat config.json
Assumed cwdpython script.pycd /workspace && python script.py
Multiple dirscd dir1; cd dir2; cmdcd dir1/dir2 && cmd

Fallback Strategy

If cd also fails:

  1. Use pwd to check current directory
  2. Use find or ls -R to locate files
  3. Verify the path structure with ls -la /path/to/check
pwd && 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Incremental audio production with duration mismatch handling, adaptive stem extension, and pre-mix alignment verification

The English summary is being prepared. Showing the original description.

HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Incremental audio production with duration alignment handling, per-stem verification, and adaptive extension strategies

The English summary is being prepared. Showing the original description.

HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Create serverless API proxy endpoints that hide API keys and provide a unified backend for the dashboard frontend. Designed for Vercel deployment.

The English summary is being prepared. Showing the original description.

HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

End-to-end audio production workflow with stems, effects, archiving, and verification

The English summary is being prepared. Showing the original description.

HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

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.

  • Continue drafting after repeated web retrieval failures
  • Preserve task requirements during network errors
  • Mark information that could not be externally verified
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Fallback pattern for executing Python code when execute_code_sandbox fails

The English summary is being prepared. Showing the original description.

HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

See all skills by HKUDS

Report a problem with this skill