[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XC06AAR0K6BY1HVYGSNEDZ":3,"skill-same:01M6XC06AAR0K6BY1HVYGSNEDZ":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":13,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M6XC06AAR0K6BY1HVYGSNEDZ","sandbox-file-discovery-and-validation",null,"Use shell tools safely in sandboxed environments by discovering files from real workspace roots instead of assumed user folders, then explicitly verifying output artifacts after generation.","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fsandbox-file-discovery-and-validation\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"sandbox","validation","file","discovery","file discovery","sandbox file discovery and validation","artifacts","Tools","shell","workspace","user","use","files","generation","output","environments","2026-11-10 10:12:30",false,"---\nname: sandbox-file-discovery-and-validation\ndescription: Use shell tools safely in sandboxed environments by discovering files from real workspace roots instead of assumed user folders, then explicitly verifying output artifacts after generation.\n---\n\n# Sandbox File Discovery and Validation\n\nUse this skill when working in constrained or sandboxed shell environments where common folders like `~\u002FDesktop`, `~\u002FDocuments`, or `~\u002FDownloads` may not exist, may be inaccessible, or may not be where task files are stored.\n\nThe goal is to:\n1. discover files from actual accessible roots,\n2. avoid brittle path assumptions,\n3. generate outputs in known locations, and\n4. explicitly validate that outputs were created and match expectations.\n\n## Core principles\n\n- Do not assume GUI-era user folders exist.\n- Start from the current working directory and other confirmed workspace roots.\n- Use recursive search from known roots, not from `\u002F` unless necessary.\n- Prefer deterministic output paths you control.\n- After creating an artifact, verify it exists, is readable, and matches the requested form.\n\n## When to use this\n\nUse this pattern when:\n- you need to locate input files in an unfamiliar sandbox,\n- the environment may be ephemeral or nonstandard,\n- you are producing files for the user,\n- success depends on the actual contents or structure of the output.\n\n## Recommended workflow\n\n### 1) Establish your real working roots\n\nBegin by identifying where you are and what directories are actually available.\n\nExample:\n`pwd`\n`ls -la`\n`find . -maxdepth 2 -type d | sort`\n\nIf needed, inspect nearby likely roots:\n`ls -la \u002Ftmp`\n`ls -la \u002Fworkspace 2>\u002Fdev\u002Fnull || true`\n`ls -la \u002Fworkspaces 2>\u002Fdev\u002Fnull || true`\n`ls -la \u002Fmnt\u002Fdata 2>\u002Fdev\u002Fnull || true`\n\nTreat only confirmed, readable directories as search roots.\n\n## 2) Avoid assumed folders\n\nDo not begin with paths like:\n- `~\u002FDesktop`\n- `~\u002FDocuments`\n- `~\u002FDownloads`\n\nunless you have already confirmed they exist and are relevant.\n\nBad:\n`find ~\u002FDesktop -name \"*.xlsx\"`\n\nBetter:\n`find . -type f -name \"*.xlsx\"`\nor, if a root is confirmed:\n`find \u002Fworkspace -type f -name \"*.xlsx\" 2>\u002Fdev\u002Fnull`\n\n## 3) Search from known roots with bounded, focused queries\n\nPrefer targeted searches over broad filesystem scans.\n\nUseful patterns:\n`find . -type f | sort`\n`find . -type f -iname \"*report*\"`\n`find . -type f \\( -iname \"*.csv\" -o -iname \"*.xlsx\" -o -iname \"*.json\" \\)`\n\nIf multiple roots are known:\n`find . \u002Fworkspace \u002Fmnt\u002Fdata -type f 2>\u002Fdev\u002Fnull | sort`\n\nGuidelines:\n- suppress permission noise with `2>\u002Fdev\u002Fnull` when appropriate,\n- filter by extension or name fragment,\n- sort output for stable inspection,\n- keep searches bounded to known roots.\n\n## 4) Choose a deterministic output location\n\nWhen generating a file, write it somewhere explicit and easy to re-check.\n\nGood patterns:\n- current directory,\n- a task-specific subdirectory like `.\u002Foutput`,\n- a confirmed writable workspace directory.\n\nExample:\n`mkdir -p output`\n`python make_result.py --out output\u002Ffinal.xlsx`\n\nAvoid writing to guessed locations that may not exist.\n\n## 5) Immediately validate the output artifact\n\nNever assume generation succeeded just because a command exited successfully.\n\nAt minimum, confirm:\n- the file exists,\n- the path is the one you intended,\n- the file is non-empty when applicable,\n- the format or structure matches the task.\n\nBasic checks:\n`ls -l output\u002Ffinal.xlsx`\n`test -f output\u002Ffinal.xlsx && echo \"exists\"`\n`test -s output\u002Ffinal.xlsx && echo \"non-empty\"`\n`file output\u002Ffinal.xlsx`\n\nFor text-like outputs:\n`head -n 20 output\u002Fresult.csv`\n`wc -l output\u002Fresult.csv`\n\nFor structured outputs, inspect with the relevant tool:\n- CSV: preview headers and row counts\n- JSON: parse and inspect keys\n- ZIP-like formats such as `.xlsx`: verify internal structure or open with a library\n- generated code\u002Fconfig: run syntax or schema checks if available\n\n## 6) Validate against task requirements, not just file existence\n\nA file existing is necessary but not sufficient.\n\nCheck the artifact against the requested deliverable:\n- expected filename or location,\n- expected sheet names, tabs, columns, or keys,\n- expected formulas, calculations, or derived values,\n- expected number of records,\n- expected transformations or formatting.\n\nExamples:\n- If a workbook was requested, verify the workbook contains the required sheets.\n- If formulas were required, verify formulas are present, not just pasted values.\n- If a filtered dataset was requested, verify row counts and selected columns.\n- If a renamed file was requested, verify the actual output name.\n\n## 7) Report with evidence\n\nWhen you finish, cite the exact artifact path and the validation you performed.\n\nGood completion style:\n- “Created `output\u002Ffinal.xlsx`.”\n- “Verified it exists and is non-empty.”\n- “Confirmed workbook contains sheets `Summary` and `Data`.”\n- “Checked that computed totals are present in column F.”\n\nThis reduces false positives where an output was produced but not actually checked.\n\n# Shell patterns to reuse\n\n## Minimal discovery sequence\n\n`pwd`\n`ls -la`\n`find . -maxdepth 3 -type f | sort`\n\n## Targeted file search\n\n`find . -type f \\( -iname \"*.xlsx\" -o -iname \"*.csv\" -o -iname \"*.tsv\" \\) | sort`\n\n## Multi-root search with graceful fallback\n\n`find . \u002Fworkspace \u002Fmnt\u002Fdata -type f 2>\u002Fdev\u002Fnull | sort`\n\n## Output creation and validation\n\n`mkdir -p output`\n`some_command > output\u002Fresult.txt`\n`test -f output\u002Fresult.txt && test -s output\u002Fresult.txt && echo \"validated\"`\n\n# Practical decision rules\n\n## Prefer this\n- `pwd` to anchor yourself\n- `find` from `.` or other verified roots\n- explicit output directories\n- post-generation checks tied to the requested deliverable\n\n## Avoid this\n- guessing user-centric folders\n- searching the entire filesystem first\n- declaring success after creation without inspection\n- reporting only the command you ran instead of what you verified\n\n# Example end-to-end pattern\n\n1. Discover roots:\n   `pwd && ls -la`\n\n2. Find candidate inputs:\n   `find . -type f \\( -iname \"*.xlsx\" -o -iname \"*.csv\" \\) | sort`\n\n3. Create controlled output location:\n   `mkdir -p output`\n\n4. Generate artifact:\n   `python transform.py input\u002Fsource.csv output\u002Ffinal.csv`\n\n5. Validate artifact exists and inspect content:\n   `ls -l output\u002Ffinal.csv`\n   `test -s output\u002Ffinal.csv`\n   `head -n 5 output\u002Ffinal.csv`\n\n6. Validate requirement-specific properties:\n   - expected headers present,\n   - row count reasonable,\n   - transformations applied.\n\n# Success criteria\n\nThis pattern is applied correctly when:\n- file discovery starts from confirmed accessible roots,\n- no critical step depends on unverified assumed directories,\n- generated artifacts are written to known locations,\n- outputs are explicitly inspected or checked,\n- final reporting includes evidence of validation.","# Sandbox File Discovery and Validation\n\nUse this skill when working in constrained or sandboxed shell environments where common folders like `~\u002FDesktop`, `~\u002FDocuments`, or `~\u002FDownloads` may not exist, may be inaccessible, or may not be where task files are stored.\n\nThe goal is to:\n1. discover files from actual accessible roots,\n2. avoid brittle path assumptions,\n3. generate outputs in known locations, and\n4. explicitly validate that outputs were created and match expectations.\n\n## Core principles\n\n- Do not assume GUI-era user folders exist.\n- Start from the current working directory and other confirmed workspace roots.\n- Use recursive search from known roots, not from `\u002F` unless necessary.\n- Prefer deterministic output paths you control.\n- After creating an artifact, verify it exists, is readable, and matches the requested form.\n\n## When to use this\n\nUse this pattern when:\n- you need to locate input files in an unfamiliar sandbox,\n- the environment may be ephemeral or nonstandard,\n- you are producing files for the user,\n- success depends on the actual contents or structure of the output.\n\n## Recommended workflow\n\n### 1) Establish your real working roots\n\nBegin by identifying where you are and what directories are actually available.\n\nExample:\n`pwd`\n`ls -la`\n`find . -maxdepth 2 -type d | sort`\n\nIf needed, inspect nearby likely roots:\n`ls -la \u002Ftmp`\n`ls -la \u002Fworkspace 2>\u002Fdev\u002Fnull || true`\n`ls -la \u002Fworkspaces 2>\u002Fdev\u002Fnull || true`\n`ls -la \u002Fmnt\u002Fdata 2>\u002Fdev\u002Fnull || true`\n\nTreat only confirmed, readable directories as search roots.\n\n## 2) Avoid assumed folders\n\nDo not begin with paths like:\n- `~\u002FDesktop`\n- `~\u002FDocuments`\n- `~\u002FDownloads`\n\nunless you have already confirmed they exist and are relevant.\n\nBad:\n`find ~\u002FDesktop -name \"*.xlsx\"`\n\nBetter:\n`find . -type f -name \"*.xlsx\"`\nor, if a root is confirmed:\n`find \u002Fworkspace -type f -name \"*.xlsx\" 2>\u002Fdev\u002Fnull`\n\n## 3) Search from known roots with bounded, focused queries\n\nPrefer targeted searches over broad filesystem scans.\n\nUseful patterns:\n`find . -type f | sort`\n`find . -type f -iname \"*report*\"`\n`find . -type f \\( -iname \"*.csv\" -o -iname \"*.xlsx\" -o -iname \"*.json\" \\)`\n\nIf multiple roots are known:\n`find . \u002Fworkspace \u002Fmnt\u002Fdata -type f 2>\u002Fdev\u002Fnull | sort`\n\nGuidelines:\n- suppress permission noise with `2>\u002Fdev\u002Fnull` when appropriate,\n- filter by extension or name fragment,\n- sort output for stable inspection,\n- keep searches bounded to known roots.\n\n## 4) Choose a deterministic output location\n\nWhen generating a file, write it somewhere explicit and easy to re-check.\n\nGood patterns:\n- current directory,\n- a task-specific subdirectory like `.\u002Foutput`,\n- a confirmed writable workspace directory.\n\nExample:\n`mkdir -p output`\n`python make_result.py --out output\u002Ffinal.xlsx`\n\nAvoid writing to guessed locations that may not exist.\n\n## 5) Immediately validate the output artifact\n\nNever assume generation succeeded just because a command exited successfully.\n\nAt minimum, confirm:\n- the file exists,\n- the path is the one you intended,\n- the file is non-empty when applicable,\n- the format or structure matches the task.\n\nBasic checks:\n`ls -l output\u002Ffinal.xlsx`\n`test -f output\u002Ffinal.xlsx && echo \"exists\"`\n`test -s output\u002Ffinal.xlsx && echo \"non-empty\"`\n`file output\u002Ffinal.xlsx`\n\nFor text-like outputs:\n`head -n 20 output\u002Fresult.csv`\n`wc -l output\u002Fresult.csv`\n\nFor structured outputs, inspect with the relevant tool:\n- CSV: preview headers and row counts\n- JSON: parse and inspect keys\n- ZIP-like formats such as `.xlsx`: verify internal structure or open with a library\n- generated code\u002Fconfig: run syntax or schema checks if available\n\n## 6) Validate against task requirements, not just file existence\n\nA file existing is necessary but not sufficient.\n\nCheck the artifact against the requested deliverable:\n- expected filename or location,\n- expected sheet names, tabs, columns, or keys,\n- expected formulas, calculations, or derived values,\n- expected number of records,\n- expected transformations or formatting.\n\nExamples:\n- If a workbook was requested, verify the workbook contains the required sheets.\n- If formulas were required, verify formulas are present, not just pasted values.\n- If a filtered dataset was requested, verify row counts and selected columns.\n- If a renamed file was requested, verify the actual output name.\n\n## 7) Report with evidence\n\nWhen you finish, cite the exact artifact path and the validation you performed.\n\nGood completion style:\n- “Created `output\u002Ffinal.xlsx`.”\n- “Verified it exists and is non-empty.”\n- “Confirmed workbook contains sheets `Summary` and `Data`.”\n- “Checked that computed totals are present in column F.”\n\nThis reduces false positives where an output was produced but not actually checked.\n\n# Shell patterns to reuse\n\n## Minimal discovery sequence\n\n`pwd`\n`ls -la`\n`find . -maxdepth 3 -type f | sort`\n\n## Targeted file search\n\n`find . -type f \\( -iname \"*.xlsx\" -o -iname \"*.csv\" -o -iname \"*.tsv\" \\) | sort`\n\n## Multi-root search with graceful fallback\n\n`find . \u002Fworkspace \u002Fmnt\u002Fdata -type f 2>\u002Fdev\u002Fnull | sort`\n\n## Output creation and validation\n\n`mkdir -p output`\n`some_command > output\u002Fresult.txt`\n`test -f output\u002Fresult.txt && test -s output\u002Fresult.txt && echo \"validated\"`\n\n# Practical decision rules\n\n## Prefer this\n- `pwd` to anchor yourself\n- `find` from `.` or other verified roots\n- explicit output directories\n- post-generation checks tied to the requested deliverable\n\n## Avoid this\n- guessing user-centric folders\n- searching the entire filesystem first\n- declaring success after creation without inspection\n- reporting only the command you ran instead of what you verified\n\n# Example end-to-end pattern\n\n1. Discover roots:\n   `pwd && ls -la`\n\n2. Find candidate inputs:\n   `find . -type f \\( -iname \"*.xlsx\" -o -iname \"*.csv\" \\) | sort`\n\n3. Create controlled output location:\n   `mkdir -p output`\n\n4. Generate artifact:\n   `python transform.py input\u002Fsource.csv output\u002Ffinal.csv`\n\n5. Validate artifact exists and inspect content:\n   `ls -l output\u002Ffinal.csv`\n   `test -s output\u002Ffinal.csv`\n   `head -n 5 output\u002Ffinal.csv`\n\n6. Validate requirement-specific properties:\n   - expected headers present,\n   - row count reasonable,\n   - transformations applied.\n\n# Success criteria\n\nThis pattern is applied correctly when:\n- file discovery starts from confirmed accessible roots,\n- no critical step depends on unverified assumed directories,\n- generated artifacts are written to known locations,\n- outputs are explicitly inspected or checked,\n- final reporting includes evidence of validation.",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","gdpval_bench\u002Fskills\u002Fsandbox-file-discovery-and-validation","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill sandbox-file-discovery-and-validation",{"tool":51,"command":52},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill sandbox-file-discovery-and-validation",{"tool":54,"command":55},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill sandbox-file-discovery-and-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fsandbox-file-discovery-and-validation\u002FSKILL.md",true,[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},".skill_id","OTHER","其他",51,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fgdpval_bench\u002Fskills\u002Fsandbox-file-discovery-and-validation\u002F.skill_id",[66,88,105,113,143,159],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":34},"01M6XCCXD3NCM2YKR3WNGBASPC","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[73,74,75,76,77,78,79,80,81,82,83,32,84,30,85,86,20,87],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","type","only","template","python",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":34},"01M6XCCT7E3J922Q345PBGSHPN","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[95,96,74,20,97,87,98,99,100,101,102,86,103,104,78,81,83],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification","with",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":34},"01M6XCCMQX1R8B6FECWB3P63T7","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[112,74,78,26,83,99,86,20,87,81],"write special chars heredoc",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":124,"publishedAt":34},"01M6XCCG41M994JJEX6VN52PEP","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\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[125,126,127,128,129,76,130,131,132,133,134,81,135,136,137,138,139,140,141,142],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":34},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[150,151,152,153,81,154,104,155,156,157,158],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":34},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[166,167,168,169,170,171,20,172,173,174],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]