Agent skill

Locate Missing Artifacts

by HKUDS in HKUDS/OpenSpace

Recover generated files in sandboxed environments by searching from confirmed roots and copying to expected locations

MITAuto-check passed

Install Locate Missing Artifacts

skills CLI
$ npx skills add HKUDS/OpenSpace --skill locate-missing-artifacts -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HKUDS/OpenSpace locate-missing-artifacts --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/gdpval/skills/locate-missing-artifacts .claude/skills/locate-missing-artifacts && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
locate-missing-artifacts
GitHub stars
7.7k
Token cost
~1k tokens
SKILL.md length
273 words
Files
2
Skills in repo
199
Repo updated
First seen
Licence
MIT

At a glance

Recover generated files in sandboxed environments by searching from confirmed roots and copying to expected locations

  • Works in 5 steps: Confirm the Failure → Identify Confirmed Root Directories → Search for the Artifact Using find → …
  • SKILL.md covers When to Use This Skill, Step-by-Step Instructions, Common Patterns and Prevention Tips, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Locate Missing Artifacts is an agent skill from HKUDS/OpenSpace. Recover generated files in sandboxed environments by searching from confirmed roots and copying to expected locations

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

The repository describes itself as: "OpenSpace: The Skill Management Layer for AI Agents" -- https://open-space.cloud/. The licence is MIT.

Example prompts

  • “/locate-missing-artifacts”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Confirm the Failure
  2. Identify Confirmed Root Directories
  3. Search for the Artifact Using find
  4. Copy Artifact to Expected Location
  5. Validate Before Proceeding

What it can do on your machine

Read from SKILL.md and the folder at commit 3827781. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Locate Missing Artifacts loads about 1k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 273 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HKUDS/OpenSpace at commit 3827781, republished under its MIT licence (© HKUDS). 273 words, ~1,040 tokens.

Download SKILL.mdSave it as .claude/skills/locate-missing-artifacts/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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
# or
test -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 check
ls -la /
ls -la $HOME
ls -la /tmp
ls -la /workspace
ls -la .
Step 3: Search for the Artifact Using find

Use find from confirmed root directories to locate the missing file:

bash
# Search by filename
find /workspace -name "filename.ext" 2>/dev/null

# Search by pattern if exact name varies
find /workspace -name "*.ext" 2>/dev/null

# Search broader paths if needed
find / -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 location
cp /found/path/filename.ext /expected/path/filename.ext

# Or if you need to preserve the original
cp -r /found/path/filename.ext /expected/path/

# Verify the copy succeeded
ls -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 readable
test -f /expected/path/filename.ext && test -r /expected/path/filename.ext && echo "Ready"

# Check file size to ensure it's not empty
stat /expected/path/filename.ext

Common Patterns

Pattern: Output Written to Wrong Directory
bash
# Tool wrote to current directory instead of specified output dir
find . -name "*.docx" -type f
cp ./report.docx ./output/report.docx
Pattern: Temporary Directory Used
bash
# File ended up in /tmp or similar
find /tmp -name "*.pdf" -mtime -1
cp /tmp/generated.pdf ./deliverables/
Pattern: Nested Subdirectory Created
bash
# Tool created extra directory levels
find /workspace -type f -name "*.xlsx"
# May find: /workspace/output/2024/reports/file.xlsx
cp /workspace/output/2024/reports/file.xlsx /workspace/deliverables/

Prevention Tips

  1. Always specify absolute paths when giving tools output locations
  2. Check the working directory before and after tool execution: pwd
  3. Verify immediately after a tool reports success before proceeding
  4. Use tool-specific confirmations when available (e.g., return paths)

Example: Complete Recovery Workflow

bash
# 1. Tool reported creating report.docx but it's missing
ls ./deliverables/report.docx
# Output: ls: cannot access './deliverables/report.docx': No such file or directory

# 2. Search for it
find /workspace -name "report.docx" 2>/dev/null
# Output: /workspace/tmp/generated/report.docx

# 3. Copy to expected location
mkdir -p ./deliverables
cp /workspace/tmp/generated/report.docx ./deliverables/report.docx

# 4. Validate
ls -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

ProblemSolution
find returns no resultsExpand search to broader paths (/, /home, /root)
Multiple matches foundCheck timestamps (-mtime -1) or file sizes to identify the correct one
Permission denied on copyUse sudo if available, or check if file is in a read-only mount
File exists but is emptyThe tool may have failed silently; regenerate the artifact

© HKUDS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in benchmarks/gdpval/skills/locate-missing-artifacts of HKUDS/OpenSpace.

  • SKILL.md
  • .skill_id

Open the folder on GitHubat commit 3827781

Compare with similar skills

Locate Missing Artifacts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Locate Missing Artifacts compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Locate Missing Artifacts this skillHKUDS/OpenSpace7.7k—~1kAutomated safety check: PassMIT
Searchdavila7/claude-code-templates32k1 repos~339Automated safety check: PassMIT
LinkedIn Job SearchMadsLorentzen/ai-job-search45k—~1.2kAutomated safety check: PassMIT
Algolia Searchdavila7/claude-code-templates32k4 repos~492Automated safety check: PassMIT
Perplexity Web Searchdavila7/claude-code-templates32k12 repos~3.5kAutomated safety check: NotesMIT
X Search via xAIcode-yeongyu/oh-my-openagent70k—~1.4kAutomated safety check: PassCustom licence

Similar skills

  • Search

    davila7/claude-code-templates

    Search Google via Bright Data SERP API. An agent skill from davila7/claude-code-templates.

    32k GitHub starsUsed in 1 repo~339 tokens
    Productivity & AutomationAuto-check passed
  • LinkedIn Job Search

    MadsLorentzen/ai-job-search

    Searches LinkedIn's public job listings for any location or remote work and fetches the full description of a posting, with no login or API key.

    45k GitHub stars~1.2k tokensUpdated 2 days ago
    Business, Finance & HRAuto-check passed
  • Algolia Search

    davila7/claude-code-templates

    Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.

    32k GitHub starsUsed in 4 repos~492 tokens
    Backend & APIsAuto-check passed
  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    32k GitHub starsUsed in 12 repos~3.5k tokens
    Research & ScienceAuto-check: notes
  • X Search via xAI

    code-yeongyu/oh-my-openagent

    Rules for using the x_search tool to search X (Twitter) through a connected xAI account: date-bound queries, trusted handles, search operators and split searches.

    70k GitHub stars~1.4k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Flox Environments

    affaan-m/ECC

    Create reproducible, cross-platform (macOS/Linux) development environments with Flox, a declarative Nix-based environment manager.

    275k GitHub starsUsed in 2 repos~3.5k tokens
    DatabasesAuto-check: notes

More from HKUDS/OpenSpace

All 199 skills in this repo
  • Walks through producing a master audio track plus stems in Python, from checking a reference file and timing sections by BPM to effects, a zip archive and final verification.

    7.7k GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Handle cascading data retrieval tool failures by falling back to embedded knowledge generation

    7.7k GitHub stars~765 tokensUpdated 1 mo ago
    Auto-check passed
  • Gives an agent a workaround when its code-execution sandbox keeps failing: save the Python script to a file and run it through the shell instead.

    7.7k GitHub stars~588 tokensUpdated 1 mo ago
    Auto-check passed
  • A recovery routine for agents whose sandboxed code runner keeps failing: save the Python script to disk, then run it through the shell and read the output.

    7.7k GitHub stars~652 tokensUpdated 1 mo ago
    Auto-check passed
  • Fallback ladder for failed sandboxed code runs, plus the habit of fixing the working directory first so generated files land in the right place.

    7.7k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Fallback workflow for executing Python code when executecodesandbox fails repeatedly

    7.7k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Locate Missing Artifacts

What does Locate Missing Artifacts do?

Recover generated files in sandboxed environments by searching from confirmed roots and copying to expected locations. Locate Missing Artifacts is an agent skill from HKUDS/OpenSpace.

How do I install Locate Missing Artifacts in Claude Code?

Run `npx skills add HKUDS/OpenSpace --skill locate-missing-artifacts -a claude-code`. Or copy the skill folder (benchmarks/gdpval/skills/locate-missing-artifacts in HKUDS/OpenSpace) into .claude/skills/locate-missing-artifacts in your project. Claude Code loads it when a task matches its description.

How do I install Locate Missing Artifacts in Codex?

Run `npx skills add HKUDS/OpenSpace --skill locate-missing-artifacts -a codex`. Or copy the skill folder (benchmarks/gdpval/skills/locate-missing-artifacts in HKUDS/OpenSpace) into .agents/skills/locate-missing-artifacts in your project. Codex loads it when a task matches its description.

Can I use Locate Missing Artifacts in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HKUDS/OpenSpace --skill locate-missing-artifacts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/locate-missing-artifacts, .gemini/skills/locate-missing-artifacts, .github/skills/locate-missing-artifacts and .opencode/skills/locate-missing-artifacts in your project.

What does Locate Missing Artifacts need to run?

SKILL.md names no scripts, command-line tools or credentials: Locate Missing Artifacts is instructions for the agent only.

Does Locate Missing Artifacts access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Locate Missing Artifacts safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Locate Missing Artifacts use?

Locate Missing Artifacts is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Locate Missing Artifacts use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Locate Missing Artifacts?

Skills that share tags, products or a category with Locate Missing Artifacts: Search (davila7/claude-code-templates, 32k stars), LinkedIn Job Search (MadsLorentzen/ai-job-search, 45k stars), Algolia Search (davila7/claude-code-templates, 32k stars) and Perplexity Web Search (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Locate Missing Artifacts?

HKUDS (a GitHub organization) maintains it in HKUDS/OpenSpace, which has 7,749 GitHub stars. The repository holds 199 skills in this directory. The repository was last updated on August 12, 2026.

Source: HKUDS/OpenSpace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.