[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KJ76RWM6HD7592ZNFN6ZDA":3,"skill-same:01M6KJ76RWM6HD7592ZNFN6ZDA":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M6KJ76RWM6HD7592ZNFN6ZDA","locate-missing-artifacts",null,"Recover generated files in sandboxed environments by searching from confirmed roots and copying to expected locations","AG064\u002FOpenSpace","AG064","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184930299?v=4","01M6KHVFG7TB73NHX3RDYSTMH2","01M6KHVFMM7XA2PZA9Z83PHS3V",0,"MIT","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Flocate-missing-artifacts\u002FSKILL.md",[],[18,19,20,21,22,23,24,25],"artifacts","missing","locate","locate missing artifacts","generated","files","environments","expected","2026-11-10 10:12:30",false,"---\nname: locate-missing-artifacts\ndescription: Recover generated files in sandboxed environments by searching from confirmed roots and copying to expected locations\n---\n\n# Locate Missing Artifacts in Sandboxed Environments\n\n## When to Use This Skill\n\nUse this skill when:\n- A tool reports success but files are not found in their expected locations\n- You receive errors like \"file not found\" after a tool claims to have created it\n- You're working in a sandboxed\u002Fephemeral environment where file paths may shift\n- Directory structure mismatches occur between tool execution and validation\n\n## Step-by-Step Instructions\n\n### Step 1: Confirm the Failure\n\nBefore searching, verify the file is actually missing from the expected location:\n\n```bash\nls -la \u002Fexpected\u002Fpath\u002Ffilename.ext\n# or\ntest -f \u002Fexpected\u002Fpath\u002Ffilename.ext && echo \"Found\" || echo \"Missing\"\n```\n\n### Step 2: Identify Confirmed Root Directories\n\nDetermine which directories you know exist and where tools typically write:\n\n```bash\n# Common roots to check\nls -la \u002F\nls -la $HOME\nls -la \u002Ftmp\nls -la \u002Fworkspace\nls -la .\n```\n\n### Step 3: Search for the Artifact Using `find`\n\nUse `find` from confirmed root directories to locate the missing file:\n\n```bash\n# Search by filename\nfind \u002Fworkspace -name \"filename.ext\" 2>\u002Fdev\u002Fnull\n\n# Search by pattern if exact name varies\nfind \u002Fworkspace -name \"*.ext\" 2>\u002Fdev\u002Fnull\n\n# Search broader paths if needed\nfind \u002F -name \"filename.ext\" 2>\u002Fdev\u002Fnull | head -20\n```\n\n### Step 4: Copy Artifact to Expected Location\n\nOnce located, explicitly copy the file to where it should be:\n\n```bash\n# Copy to expected location\ncp \u002Ffound\u002Fpath\u002Ffilename.ext \u002Fexpected\u002Fpath\u002Ffilename.ext\n\n# Or if you need to preserve the original\ncp -r \u002Ffound\u002Fpath\u002Ffilename.ext \u002Fexpected\u002Fpath\u002F\n\n# Verify the copy succeeded\nls -la \u002Fexpected\u002Fpath\u002Ffilename.ext\n```\n\n### Step 5: Validate Before Proceeding\n\nConfirm the file is now accessible at the expected location:\n\n```bash\n# Test file exists and is readable\ntest -f \u002Fexpected\u002Fpath\u002Ffilename.ext && test -r \u002Fexpected\u002Fpath\u002Ffilename.ext && echo \"Ready\"\n\n# Check file size to ensure it's not empty\nstat \u002Fexpected\u002Fpath\u002Ffilename.ext\n```\n\n## Common Patterns\n\n### Pattern: Output Written to Wrong Directory\n\n```bash\n# Tool wrote to current directory instead of specified output dir\nfind . -name \"*.docx\" -type f\ncp .\u002Freport.docx .\u002Foutput\u002Freport.docx\n```\n\n### Pattern: Temporary Directory Used\n\n```bash\n# File ended up in \u002Ftmp or similar\nfind \u002Ftmp -name \"*.pdf\" -mtime -1\ncp \u002Ftmp\u002Fgenerated.pdf .\u002Fdeliverables\u002F\n```\n\n### Pattern: Nested Subdirectory Created\n\n```bash\n# Tool created extra directory levels\nfind \u002Fworkspace -type f -name \"*.xlsx\"\n# May find: \u002Fworkspace\u002Foutput\u002F2024\u002Freports\u002Ffile.xlsx\ncp \u002Fworkspace\u002Foutput\u002F2024\u002Freports\u002Ffile.xlsx \u002Fworkspace\u002Fdeliverables\u002F\n```\n\n## Prevention Tips\n\n1. **Always specify absolute paths** when giving tools output locations\n2. **Check the working directory** before and after tool execution: `pwd`\n3. **Verify immediately** after a tool reports success before proceeding\n4. **Use tool-specific confirmations** when available (e.g., return paths)\n\n## Example: Complete Recovery Workflow\n\n```bash\n# 1. Tool reported creating report.docx but it's missing\nls .\u002Fdeliverables\u002Freport.docx\n# Output: ls: cannot access '.\u002Fdeliverables\u002Freport.docx': No such file or directory\n\n# 2. Search for it\nfind \u002Fworkspace -name \"report.docx\" 2>\u002Fdev\u002Fnull\n# Output: \u002Fworkspace\u002Ftmp\u002Fgenerated\u002Freport.docx\n\n# 3. Copy to expected location\nmkdir -p .\u002Fdeliverables\ncp \u002Fworkspace\u002Ftmp\u002Fgenerated\u002Freport.docx .\u002Fdeliverables\u002Freport.docx\n\n# 4. Validate\nls -la .\u002Fdeliverables\u002Freport.docx\n# Output: -rw-r--r-- 1 user user 45678 Jan 15 10:30 .\u002Fdeliverables\u002Freport.docx\n\n# Success - file is now where it should be\n```\n\n## Troubleshooting\n\n| Problem | Solution |\n|---------|----------|\n| `find` returns no results | Expand search to broader paths (`\u002F`, `\u002Fhome`, `\u002Froot`) |\n| Multiple matches found | Check timestamps (`-mtime -1`) or file sizes to identify the correct one |\n| Permission denied on copy | Use `sudo` if available, or check if file is in a read-only mount |\n| File exists but is empty | The tool may have failed silently; regenerate the artifact |","# Locate Missing Artifacts in Sandboxed Environments\n\n## When to Use This Skill\n\nUse this skill when:\n- A tool reports success but files are not found in their expected locations\n- You receive errors like \"file not found\" after a tool claims to have created it\n- You're working in a sandboxed\u002Fephemeral environment where file paths may shift\n- Directory structure mismatches occur between tool execution and validation\n\n## Step-by-Step Instructions\n\n### Step 1: Confirm the Failure\n\nBefore searching, verify the file is actually missing from the expected location:\n\n```bash\nls -la \u002Fexpected\u002Fpath\u002Ffilename.ext\n# or\ntest -f \u002Fexpected\u002Fpath\u002Ffilename.ext && echo \"Found\" || echo \"Missing\"\n```\n\n### Step 2: Identify Confirmed Root Directories\n\nDetermine which directories you know exist and where tools typically write:\n\n```bash\n# Common roots to check\nls -la \u002F\nls -la $HOME\nls -la \u002Ftmp\nls -la \u002Fworkspace\nls -la .\n```\n\n### Step 3: Search for the Artifact Using `find`\n\nUse `find` from confirmed root directories to locate the missing file:\n\n```bash\n# Search by filename\nfind \u002Fworkspace -name \"filename.ext\" 2>\u002Fdev\u002Fnull\n\n# Search by pattern if exact name varies\nfind \u002Fworkspace -name \"*.ext\" 2>\u002Fdev\u002Fnull\n\n# Search broader paths if needed\nfind \u002F -name \"filename.ext\" 2>\u002Fdev\u002Fnull | head -20\n```\n\n### Step 4: Copy Artifact to Expected Location\n\nOnce located, explicitly copy the file to where it should be:\n\n```bash\n# Copy to expected location\ncp \u002Ffound\u002Fpath\u002Ffilename.ext \u002Fexpected\u002Fpath\u002Ffilename.ext\n\n# Or if you need to preserve the original\ncp -r \u002Ffound\u002Fpath\u002Ffilename.ext \u002Fexpected\u002Fpath\u002F\n\n# Verify the copy succeeded\nls -la \u002Fexpected\u002Fpath\u002Ffilename.ext\n```\n\n### Step 5: Validate Before Proceeding\n\nConfirm the file is now accessible at the expected location:\n\n```bash\n# Test file exists and is readable\ntest -f \u002Fexpected\u002Fpath\u002Ffilename.ext && test -r \u002Fexpected\u002Fpath\u002Ffilename.ext && echo \"Ready\"\n\n# Check file size to ensure it's not empty\nstat \u002Fexpected\u002Fpath\u002Ffilename.ext\n```\n\n## Common Patterns\n\n### Pattern: Output Written to Wrong Directory\n\n```bash\n# Tool wrote to current directory instead of specified output dir\nfind . -name \"*.docx\" -type f\ncp .\u002Freport.docx .\u002Foutput\u002Freport.docx\n```\n\n### Pattern: Temporary Directory Used\n\n```bash\n# File ended up in \u002Ftmp or similar\nfind \u002Ftmp -name \"*.pdf\" -mtime -1\ncp \u002Ftmp\u002Fgenerated.pdf .\u002Fdeliverables\u002F\n```\n\n### Pattern: Nested Subdirectory Created\n\n```bash\n# Tool created extra directory levels\nfind \u002Fworkspace -type f -name \"*.xlsx\"\n# May find: \u002Fworkspace\u002Foutput\u002F2024\u002Freports\u002Ffile.xlsx\ncp \u002Fworkspace\u002Foutput\u002F2024\u002Freports\u002Ffile.xlsx \u002Fworkspace\u002Fdeliverables\u002F\n```\n\n## Prevention Tips\n\n1. **Always specify absolute paths** when giving tools output locations\n2. **Check the working directory** before and after tool execution: `pwd`\n3. **Verify immediately** after a tool reports success before proceeding\n4. **Use tool-specific confirmations** when available (e.g., return paths)\n\n## Example: Complete Recovery Workflow\n\n```bash\n# 1. Tool reported creating report.docx but it's missing\nls .\u002Fdeliverables\u002Freport.docx\n# Output: ls: cannot access '.\u002Fdeliverables\u002Freport.docx': No such file or directory\n\n# 2. Search for it\nfind \u002Fworkspace -name \"report.docx\" 2>\u002Fdev\u002Fnull\n# Output: \u002Fworkspace\u002Ftmp\u002Fgenerated\u002Freport.docx\n\n# 3. Copy to expected location\nmkdir -p .\u002Fdeliverables\ncp \u002Fworkspace\u002Ftmp\u002Fgenerated\u002Freport.docx .\u002Fdeliverables\u002Freport.docx\n\n# 4. Validate\nls -la .\u002Fdeliverables\u002Freport.docx\n# Output: -rw-r--r-- 1 user user 45678 Jan 15 10:30 .\u002Fdeliverables\u002Freport.docx\n\n# Success - file is now where it should be\n```\n\n## Troubleshooting\n\n| Problem | Solution |\n|---------|----------|\n| `find` returns no results | Expand search to broader paths (`\u002F`, `\u002Fhome`, `\u002Froot`) |\n| Multiple matches found | Check timestamps (`-mtime -1`) or file sizes to identify the correct one |\n| Permission denied on copy | Use `sudo` if available, or check if file is in a read-only mount |\n| File exists but is empty | The tool may have failed silently; regenerate the artifact |",{"name":5,"description":7},"main","ff671ef61ed6587c49bd54c81cdc751c0b99e363","gdpval_bench\u002Fskills\u002Flocate-missing-artifacts","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace","https:\u002F\u002Fgithub.com\u002FAG064","AG064, E.Mi.\r\n\r\nA person who thinks all the time, yet all they have to think about is nothing. I want to improve the world and work on open source projects","2026-10-08 06:53:48",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add AG064\u002FOpenSpace --skill locate-missing-artifacts",{"tool":44,"command":45},"bunx","bunx skills add AG064\u002FOpenSpace --skill locate-missing-artifacts",{"tool":47,"command":48},"pnpm","pnpm dlx skills add AG064\u002FOpenSpace --skill locate-missing-artifacts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Flocate-missing-artifacts\u002FSKILL.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},".skill_id","OTHER","其他",38,"https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Flocate-missing-artifacts\u002F.skill_id",[59,82,99,108,138,154],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":26},"01M6KKMPWA0B5SCCH766F8M5EA","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.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[66,67,68,69,70,71,72,73,74,75,76,23,77,78,79,80,81],"write special chars ts check","check","write","filters","Existing","type-checking","for","errors","script","output","type","only","template","file","python","typescript",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":26},"01M6KKMJXVBNVEY3TRK055F4A7","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 \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[89,90,68,78,91,92,79,80,93,94,95,96,97,72,74,98],"readback","write special chars readback","cleanup","read","scripts","verification","via","post","helper","with",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":26},"01M6KKMEGX9M9NC105J0W3Q5B9","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[68,106,80,72,95,78,107,79,74],"write special chars heredoc","shell",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":119,"publishedAt":26},"01M6KKM8EJ2AATVHZBNB916WT0","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[120,121,122,123,81,124,125,126,127,128,72,129,130,131,132,133,134,135,136,137],"reference","worldmonitor","worldmonitor reference","dashboard","css","architecture","extracting","hierarchy","source","layer","panel","patterns","edge functions","integrations","open","api","data","scheduler",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":26},"01M6KKM39PHYK627F19GE2B9XN","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[145,146,147,148,72,149,98,150,151,152,153],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":26},"01M6KKKY7T2P61Y0JH54CDEJKQ","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[161,162,163,164,165,166,79,167,168,169],"directory","verify","structure","verify directory structure","access","first","issues","diagnose","file access"]