Skip to content
cccskills
FreePublished on GitHub

file-locate-verify

Locate missing files and verify their full paths before processing them. This workflow checks directory contents, searches by filename, and inspects permissions, size, and modification time to help resolve FileNotFoundError, an error indicating a file could not be found.

OriginalShow the original description

Systematic workflow to resolve FileNotFoundError by locating and verifying file paths

Works withExcel
See how to install

Good for

  • Investigating FileNotFoundError
  • Finding files with unknown locations
  • Checking file existence and permissions before processing

Files included (2)

  • SKILL.md3.3 KB
  • .skill_id32 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

File Locate and Verify Workflow

When encountering FileNotFoundError or uncertain file paths, follow this systematic pattern to safely locate and verify files before executing operations.

When to Use

  • You receive a FileNotFoundError or similar path-related error
  • You need to work with files whose exact location is unknown
  • You want to verify file existence before executing operations that depend on those files

Step-by-Step Procedure

Step 1: Check Current Directory Contents

First, use list_dir to inspect what files exist in your current working directory:

# Use the list_dir tool to see current directory contents
list_dir(path=".")

This reveals files in the immediate context and helps determine if you need to search elsewhere.

Step 2: Search for the File Using Find

If the file is not in the current directory, use the find command to locate it by name:

# Search for a specific file by name (case-insensitive)
find . -iname "filename.pdf" 2>/dev/null

# Or search from root for system-wide files
find / -name "filename.pdf" 2>/dev/null

Tips:

  • Use -iname for case-insensitive matching
  • Redirect stderr with 2>/dev/null to suppress permission errors
  • Narrow the search scope when possible for better performance

Step 3: Verify the Discovered Path

Before executing any operations on the discovered file, verify it exists and check its properties:

# Verify file existence and permissions at the full path
ls -la /full/path/to/discovered/file.pdf

This confirms:

  • The file actually exists at the located path
  • File permissions (can you read/write it?)
  • File size and modification time

Step 4: Execute Your Operation Safely

Only after verification, proceed with your intended operation:

# Now safe to work with the verified path
file_path = "/full/path/to/discovered/file.pdf"
# ... your extraction or processing code here

Complete Example

# Task: Process a file that may be in an unknown location

# Step 1: Check current directory
dir_contents = list_dir(path=".")
print(f"Current directory contains: {dir_contents}")

# Step 2: Find the file if not present
if "target_file.xlsx" not in dir_contents:
    result = run_shell(command='find . -iname "target_file.xlsx" 2>/dev/null')
    file_path = result.stdout.strip().split('\n')[0]
    print(f"Found file at: {file_path}")

# Step 3: Verify before proceeding
verification = run_shell(command=f'ls -la {file_path}')
print(f"Verification: {verification.stdout}")

# Step 4: Proceed with operation
# ... your code to process the file

Common Pitfalls to Avoid

  1. Skipping verification: Never assume the path from find is correct without checking
  2. Using relative paths blindly: Always convert to absolute paths when possible
  3. Ignoring permissions: ls -la reveals if you have read/write access
  4. Hardcoding paths: Always dynamically locate files when location is uncertain

Related Tools

  • list_dir: Inspect directory contents
  • run_shell: Execute find and ls commands
  • read_file: Read file contents after verification
  • shell_agent: Delegate complex file operations after path is confirmed

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

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.

  • Match audio parts with different durations
  • Extend drums and melodic parts using suitable methods
  • Check audio specifications before mixing
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

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.

  • Align instrument tracks to a reference audio file
  • Choose how to extend tracks that are too short
  • Verify audio properties after generation and effects
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

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.

  • Connect a dashboard to external APIs without exposing API keys
  • Create endpoints for stock quotes and news
  • Standardize API responses and error handling
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

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.

  • Export a master track with separate audio parts
  • Apply filters and reverb to audio
  • Check duration and format across deliverables
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

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.

  • Retry Python work through the shell after repeated sandbox failures
  • Run longer tasks with an adjusted timeout
  • Execute Python work that needs multiple files or system utilities
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

See all skills by HKUDS

Report a problem with this skill