<< All versions
Step 3: Search for the Artifact Using
Skill v1.0.2
Automated scan100/100hkuds/openspace/locate-missing-artifacts
1 files
──Details
PublishedApril 26, 2026 at 04:15 PM
Content Hashsha256:a2105d75a9a917d4...
Git SHAd1e367d0ed47
Bump Typepatch
──Files
Files (1 file, 4.1 KB)
SKILL.md4.1 KBactive
SKILL.md · 147 lines · 4.1 KB
version: "1.0.2" name: locate-missing-artifacts description: Recover generated files in sandboxed environments by searching from confirmed roots and copying to expected locations
Locate Missing Artifacts in Sandboxed Environments
When to Use This Skill
Use this skill when:
- A tool reports success but files are not found in their expected locations
- You receive errors like "file not found" after a tool claims to have created it
- You're working in a sandboxed/ephemeral environment where file paths may shift
- Directory structure mismatches occur between tool execution and validation
Step-by-Step Instructions
Step 1: Confirm the Failure
Before searching, verify the file is actually missing from the expected location:
bash
ls -la /expected/path/filename.ext# ortest -f /expected/path/filename.ext && echo "Found" || echo "Missing"
Step 2: Identify Confirmed Root Directories
Determine which directories you know exist and where tools typically write:
bash
# Common roots to checkls -la /ls -la $HOMEls -la /tmpls -la /workspacels -la .
Step 3: Search for the Artifact Using find
Use find from confirmed root directories to locate the missing file:
bash
# Search by filenamefind /workspace -name "filename.ext" 2>/dev/null# Search by pattern if exact name variesfind /workspace -name "*.ext" 2>/dev/null# Search broader paths if neededfind / -name "filename.ext" 2>/dev/null | head -20
Step 4: Copy Artifact to Expected Location
Once located, explicitly copy the file to where it should be:
bash
# Copy to expected locationcp /found/path/filename.ext /expected/path/filename.ext# Or if you need to preserve the originalcp -r /found/path/filename.ext /expected/path/# Verify the copy succeededls -la /expected/path/filename.ext
Step 5: Validate Before Proceeding
Confirm the file is now accessible at the expected location:
bash
# Test file exists and is readabletest -f /expected/path/filename.ext && test -r /expected/path/filename.ext && echo "Ready"# Check file size to ensure it's not emptystat /expected/path/filename.ext
Common Patterns
Pattern: Output Written to Wrong Directory
bash
# Tool wrote to current directory instead of specified output dirfind . -name "*.docx" -type fcp ./report.docx ./output/report.docx
Pattern: Temporary Directory Used
bash
# File ended up in /tmp or similarfind /tmp -name "*.pdf" -mtime -1cp /tmp/generated.pdf ./deliverables/
Pattern: Nested Subdirectory Created
bash
# Tool created extra directory levelsfind /workspace -type f -name "*.xlsx"# May find: /workspace/output/2024/reports/file.xlsxcp /workspace/output/2024/reports/file.xlsx /workspace/deliverables/
Prevention Tips
- Always specify absolute paths when giving tools output locations
- Check the working directory before and after tool execution:
pwd - Verify immediately after a tool reports success before proceeding
- Use tool-specific confirmations when available (e.g., return paths)
Example: Complete Recovery Workflow
bash
# 1. Tool reported creating report.docx but it's missingls ./deliverables/report.docx# Output: ls: cannot access './deliverables/report.docx': No such file or directory# 2. Search for itfind /workspace -name "report.docx" 2>/dev/null# Output: /workspace/tmp/generated/report.docx# 3. Copy to expected locationmkdir -p ./deliverablescp /workspace/tmp/generated/report.docx ./deliverables/report.docx# 4. Validatels -la ./deliverables/report.docx# Output: -rw-r--r-- 1 user user 45678 Jan 15 10:30 ./deliverables/report.docx# Success - file is now where it should be
Troubleshooting
| Problem | Solution | |
|---|---|---|
find returns no results | Expand search to broader paths (/, /home, /root) | |
| Multiple matches found | Check timestamps (-mtime -1) or file sizes to identify the correct one | |
| Permission denied on copy | Use sudo if available, or check if file is in a read-only mount | |
| File exists but is empty | The tool may have failed silently; regenerate the artifact |