file-locate-verify
Systematic workflow to resolve FileNotFoundError by locating and verifying file paths
- License 许可
- MIT
- 所属仓库
- HKUDS/AgentPilot
- 最近更新
- 2026-11-12
- Stars
- ★ 8.0k
- Forks
- 944
01 前言 Front Matter
- name
- file-locate-verify
- description
- Systematic workflow to resolve FileNotFoundError by locating and verifying file paths
02 资源文件 1
- 其他.skill_id32 B
03 SKILL.md 正文
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
-inamefor case-insensitive matching - Redirect stderr with
2>/dev/nullto 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
- Skipping verification: Never assume the path from
findis correct without checking - Using relative paths blindly: Always convert to absolute paths when possible
- Ignoring permissions:
ls -lareveals if you have read/write access - Hardcoding paths: Always dynamically locate files when location is uncertain
Related Tools
list_dir: Inspect directory contentsrun_shell: Execute find and ls commandsread_file: Read file contents after verificationshell_agent: Delegate complex file operations after path is confirmed
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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 /tmp helper scripts.