[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70JCJ0D4H2KXSNXNEY93ZX6":3,"skill-same:01M70JCJ0D4H2KXSNXNEY93ZX6":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":6,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M70JCJ0D4H2KXSNXNEY93ZX6","tree_gen",null,"Generate a professional ASCII directory structure in Markdown. Use this before modifying a project to understand its layout, identify key files, visualize or document the file structure of a directory, project or codebase.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Ftree_gen\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"tree","tree gen","system","visualize","list","directory","markdown","human","layout","generate","project structure","structure","documentation","team","files","project","file-system","professional","show","visualization","2026-11-10 10:12:30",false,"---\nname: \"tree_gen\"\ndescription: \"Generate a professional ASCII directory structure in Markdown. Use this before modifying a project to understand its layout, identify key files, visualize or document the file structure of a directory, project or codebase.\"\nversion: \"1.0.0\"\nauthor: \"Human Skill Team\"\ntags: [\"documentation\", \"structure\", \"visualization\", \"tree\", \"file-system\"]\ntrigger_patterns:\n  - \"directory structure\"\n  - \"file tree\"\n  - \"show structure\"\n  - \"visualize folder\"\n  - \"project structure\"\n  - \"codebase tree\"\n  - \"list files\"\n  - \"dir structure\"\n---\n\n# Directory Structure Generator\n\n## When to Use\n\nActivate this skill when the user asks to:\n- Understand the directory structure of a project\n- Show the directory structure of a project\n- Visualize the file tree of a codebase\n- Document the folder organization\n- List files in a structured format\n- Generate a markdown representation of a directory\n\n## The **tree_gen** Tool\n\nThis skill uses the `tree_gen` tool to create Markdown-formatted directory trees.\n\n### 📝 PARAMETERS:\n- `input_path`: **REQUIRED** - Absolute path of the directory to scan.\n- `output_path`: *OPTIONAL* - Where to write the output file. Defaults to `input_path`.\n- `file_name`: *OPTIONAL* - Output filename. Defaults to `{dir_name}_structure.md`.\n- `layout`: *OPTIONAL* - `\"vertical\"` (default, classic top-down) or `\"horizontal\"` (top-level dirs side-by-side).\n- `max_depth`: *OPTIONAL* - How many levels deep to recurse. Default: `4`. Set `0` for unlimited.\n- `use_gitignore`: *OPTIONAL* - Read and apply `.gitignore` rules. Default: `true`.\n- `ignored_path`: *OPTIONAL* - Comma-separated absolute paths to exclude.\n- `ignored_extensions`: *OPTIONAL* - Comma-separated extensions to exclude (e.g. `.log,.tmp`).\n\n\n## Decision Tree: How to Use This Tool\n\n### 1️⃣ Identify the Scope\n\n**Ask yourself:**\n- Is this a small project (\u003C100 files)?\n- Is this a large codebase (>1000 files)?\n- Does the user want the full project or a specific folder?\n- Do they want all files or just source code?\n\n### 2️⃣ Choose the Right Strategy\n\n| Scenario | Strategy |\n|----------|----------|\n| **Small project** | Scan everything, minimal ignores |\n| **Medium web app** | Ignore node_modules, build outputs |\n| **Large monorepo** | Target specific directories, aggressive ignores |\n| **Root-level scan** | Always ignore knowledge, chats, workdir |\n| **Source code only** | Ignore all non-code files |\n\n---\n\n### 📋 HOW TO CALL THIS TOOL:\n\nThe agent executes `execute.py` with the JSON payload passed directly as a string argument:\n\n```bash\nhuman-skills '{\"tool_name\": \"tree_gen\", \"tool_args\": {\"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\", \"output_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\", \"file_name\": \"PROJECT_MAP\", \"layout\": \"vertical\", \"max_depth\": \"3\", \"use_gitignore\": \"true\", \"ignored_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Ftests, home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Fdocs\", \"ignored_extensions\": \".csv,.json\"}}'\n```\n\nWhich maps to this JSON payload:\n```json\n{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\":         \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\",\n        \"output_path\":        \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\",\n        \"file_name\":          \"PROJECT_MAP\",\n        \"layout\":             \"vertical\",\n        \"max_depth\":          \"3\",\n        \"use_gitignore\":      \"true\",\n        \"ignored_path\":       \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Ftests, home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Fdocs\",\n        \"ignored_extensions\": \".csv,.json\"\n    }\n}\n```\n\nExpected output:\n```\n✅ Directory Structure Generated.\n   Path    : home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002FPROJECT_MAP.md\n   Layout  : vertical\n   Depth   : 3 levels\n   Lines   : 33\n   Size    : 986.0 B\n   Dirs    : 15\n   Files   : 26\n   Scanned : 282.2 KB\n```\n\n### ⚠️ IMPORTANT NOTES:\n- **All values in `tool_args` must be strings** (e.g. `\"max_depth\": \"3\"`, not `3`).\n- Common patterns (`.git`, `node_modules`, `__pycache__`, binaries, media) are auto-ignored.\n- If output exceeds 500 lines, a tip is shown to reduce `max_depth` or add `ignored_path`.\n- Default filename: `{dir_name}_structure.md` (e.g. `my-project_structure.md`).\n\n## Scenario-Based Instructions\n\n### 📁 Scenario 1: Small Project (\u003C 100 files)\n\n**When:** Scanning a small Python project, simple script, or personal library where we want to show almost everything, ignoring only cache and git files, using the default depth of 4.\n\n**What to ignore:** Minimal - only critical clutter\n- `__pycache__`, `.git`, `.venv`, `node_modules`\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-folder\",\n        \"ignored_path\": \"__pycache__, .git, .venv, .env, .gitkeep, .DS_Store, .log, .tmp\"\n    }\n}'\n```\n\n---\n\n### 📦 Scenario 2: Medium Web Application (100–1000 files)\n\n**When:** Scanning a typical React, Vue, or Node.js web app where we need to ignore dependencies and build outputs for a cleaner overview.\n\n**What to ignore:** Dependencies and build artifacts\n- `node_modules`, `dist`, `build`, `coverage`\n- `.next`, `.nuxt`, `.cache`\n- `__pycache__`, `.pytest_cache`\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-webapp\",\n        \"ignored_path\": \"node_modules, dist, .next, coverage, __pycache__, .git, .venv, .env, .gitkeep, .DS_Store, .log, .tmp\"\n    }\n}'\n```\n\n---\n\n### 🏢 Scenario 3: Large Codebase\u002FMonorepo (> 1000 files)\n\n**When:** Scanning an enterprise application, complex system, or a specific package within a large monorepo. We must ignore tests and dependencies to keep the output manageable.\n\n**Strategy:** \n1. **Never scan the entire root** - it will be too large\n2. **Target specific packages\u002Fmodules** one at a time\n3. **Use aggressive ignores**\n\n**What to ignore:** Everything non-essential\n- All dependencies: `node_modules`, `vendor`, `.venv`\n- All build outputs: `dist`, `build`, `out`, `target`\n- All test files and coverage\n- All media and assets\n\n**Example - Scan specific package:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmonorepo\u002Fpackages\u002Fbackend\",\n        \"ignored_path\": \"node_modules, dist, coverage, tests, __tests__, .git\"\n    }\n}'\n```\n\n**Example - Multiple targeted scans:**\n```bash\n# First: Backend\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmonorepo\u002Fpackages\u002Fbackend\",\n        \"output_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fdocs\",\n        \"ignored_path\": \"node_modules, dist, tests\"\n    }\n}'\n\n# Then: Frontend (separate call)\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmonorepo\u002Fpackages\u002Ffrontend\",\n        \"output_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fdocs\",\n        \"ignored_path\": \"node_modules, .next, public\u002Fassets\"\n    }\n}'\n```\n\n---\n\n### 🌍 Scenario 4: Root-Level Scan (home\u002Fuser_name\u002F or system root)\n\n**When:** Generating a system-wide or root workspace overview. We must aggressively ignore huge directories like workdir, chats, and knowledge to prevent overflowing the token limit.\n\n**⚠️ CRITICAL RULES:**\n1. **ALWAYS ignore these paths for home\u002Fuser_name\u002F:**\n   - `home\u002Fuser_name\u002Fworkdir` (user projects - scan separately)\n   - `home\u002Fuser_name\u002Fchats` (conversation history)\n   - `home\u002Fuser_name\u002Fknowledge\u002Fmain` (large knowledge base)\n   - `home\u002Fuser_name\u002Fmemory\u002Fdefault` (vector database)\n\n2. **What to show:**\n   - Agent configurations\n   - Skills\n   - System configuration files\n   - Project metadata\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002F\",\n        \"ignored_path\": \"home\u002Fuser_name\u002Fworkdir, home\u002Fuser_name\u002Fchats, home\u002Fuser_name\u002Fknowledge\u002Fmain, home\u002Fuser_name\u002Fmemory\u002Fdefault\"\n    }\n}'\n```\n\n---\n\n### 🎯 Scenario 5: Specific Folder Deep Dive\n\n**When:** The user requests a deep dive into ONE specific directory (e.g., \"show me the src folder structure\"). We need to show all source files with minimal filtering.\n\n**Strategy:**\n- Target ONLY that folder\n- Show everything inside (minimal ignores)\n- Good for code review, onboarding, documentation\n\n**What to ignore:** Only cache and temporary files\n- `__pycache__`, `.pytest_cache`\n- `*.pyc`, `.DS_Store`\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-app\u002Fsrc\",\n        \"ignored_path\": \"__pycache__, .pytest_cache\"\n    }\n}'\n```\n\n---\n\n### 📝 Scenario 6: Documentation Purpose\n\n**When:** Preparing structure output for a README, documentation, or architectural diagram. We should only show source code and configuration, strictly hiding test suites and build outputs.\n\n**Strategy:**\n- Focus on source code and configuration\n- Ignore everything that's not essential to understanding\n- Keep output clean and professional\n\n**What to ignore:**\n- All dependencies and node_modules\n- All build outputs and artifacts\n- All test files (unless specifically asked)\n- All media and binary files\n- All local development files (.env, .vscode)\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\",\n        \"output_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Fdocs\",\n        \"ignored_path\": \"node_modules, dist, build, tests, __tests__, coverage, .git, .vscode, public\u002Fimages\"\n    }\n}'\n```\n\n---\n\n## Quick Reference: Common Ignore Patterns\n\n### By Language\u002FFramework\n\n**Python Projects:**\n```\n__pycache__, .pytest_cache, .venv, .mypy_cache, *.pyc, dist, build\n```\n\n**Node.js Projects:**\n```\nnode_modules, dist, build, .next, .nuxt, coverage, .cache\n```\n\n**Full-Stack Projects:**\n```\nnode_modules, __pycache__, dist, build, .venv, coverage, .git\n```\n\n### By Purpose\n\n**Code Review (show source only):**\n```\nnode_modules, dist, build, tests, __tests__, coverage, docs, public\n```\n\n**Documentation (clean view):**\n```\nnode_modules, dist, .git, .vscode, tests, coverage, *.min.js, assets\n```\n\n**Deployment Check (show build outputs):**\n```\nnode_modules, .git, src, tests (only ignore source and development files)\n```\n\n---\n\n## Best Practices\n\n### ✅ DO:\n1. **Always check project size first** - use `list_dir` to estimate\n2. **For large projects, scan specific directories** - never scan massive roots\n3. **For home\u002Fuser_name\u002F, ALWAYS ignore workdir and chats**\n4. **Match ignores to user's intent** - code review vs documentation needs different ignores\n5. **Present the output** - read structure.md and show it to user after generation\n\n### ❌ DON'T:\n1. **Don't scan home\u002Fuser_name\u002Fworkdir directly** - ask which project inside it\n2. **Don't forget node_modules** - it can have 100k+ files\n3. **Don't ignore too little** - output will be overwhelming\n4. **Don't use relative paths in ignored_path** - always use absolute paths\n5. **Don't generate without understanding user's goal** - ask if unclear\n\n---\n\n## Common Issues & Solutions\n\n| Issue | Solution |\n|-------|----------|\n| \"Output is 10,000+ lines\" | Add more aggressive ignores or target smaller directory |\n| \"Empty structure.md\" | Path doesn't exist or all files were ignored |\n| \"Still showing node_modules\" | Use absolute path: `\u002Ffull\u002Fpath\u002Fto\u002Fnode_modules` |\n| \"Missing important files\" | Review ignored_path - may have over-filtered |\n\n## Troubleshooting\n\n### Issue: Empty Output\n\n**Cause:** Directory doesn't exist or is empty.\n**Solution:** Verify the path exists with `list_dir` first.\n\n### Issue: Too Much Output\n\n**Cause:** Not enough ignore patterns.\n**Solution:** Add more paths\u002Fextensions to ignore, or generate subdirectories separately.\n\n### Issue: File Not Found\n\n**Cause:** Output directory doesn't exist.\n**Solution:** Create output directory first or use existing path.\n\n## Output Format\n\nThe generated `structure.md` file contains:\n- Markdown-formatted tree structure\n- File and folder counts\n- List of ignored paths\u002Fpatterns\n- Generation timestamp\n\nExample output:\n```markdown\n## file tree\n\u002Fmy-project\u002F\n├── src\u002F\n│   ├── main.py\n│   └── utils\u002F\n│       └── helpers.py\n├── tests\u002F\n│   └── test_main.py\n└── README.md\n```","# Directory Structure Generator\n\n## When to Use\n\nActivate this skill when the user asks to:\n- Understand the directory structure of a project\n- Show the directory structure of a project\n- Visualize the file tree of a codebase\n- Document the folder organization\n- List files in a structured format\n- Generate a markdown representation of a directory\n\n## The **tree_gen** Tool\n\nThis skill uses the `tree_gen` tool to create Markdown-formatted directory trees.\n\n### 📝 PARAMETERS:\n- `input_path`: **REQUIRED** - Absolute path of the directory to scan.\n- `output_path`: *OPTIONAL* - Where to write the output file. Defaults to `input_path`.\n- `file_name`: *OPTIONAL* - Output filename. Defaults to `{dir_name}_structure.md`.\n- `layout`: *OPTIONAL* - `\"vertical\"` (default, classic top-down) or `\"horizontal\"` (top-level dirs side-by-side).\n- `max_depth`: *OPTIONAL* - How many levels deep to recurse. Default: `4`. Set `0` for unlimited.\n- `use_gitignore`: *OPTIONAL* - Read and apply `.gitignore` rules. Default: `true`.\n- `ignored_path`: *OPTIONAL* - Comma-separated absolute paths to exclude.\n- `ignored_extensions`: *OPTIONAL* - Comma-separated extensions to exclude (e.g. `.log,.tmp`).\n\n\n## Decision Tree: How to Use This Tool\n\n### 1️⃣ Identify the Scope\n\n**Ask yourself:**\n- Is this a small project (\u003C100 files)?\n- Is this a large codebase (>1000 files)?\n- Does the user want the full project or a specific folder?\n- Do they want all files or just source code?\n\n### 2️⃣ Choose the Right Strategy\n\n| Scenario | Strategy |\n|----------|----------|\n| **Small project** | Scan everything, minimal ignores |\n| **Medium web app** | Ignore node_modules, build outputs |\n| **Large monorepo** | Target specific directories, aggressive ignores |\n| **Root-level scan** | Always ignore knowledge, chats, workdir |\n| **Source code only** | Ignore all non-code files |\n\n---\n\n### 📋 HOW TO CALL THIS TOOL:\n\nThe agent executes `execute.py` with the JSON payload passed directly as a string argument:\n\n```bash\nhuman-skills '{\"tool_name\": \"tree_gen\", \"tool_args\": {\"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\", \"output_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\", \"file_name\": \"PROJECT_MAP\", \"layout\": \"vertical\", \"max_depth\": \"3\", \"use_gitignore\": \"true\", \"ignored_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Ftests, home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Fdocs\", \"ignored_extensions\": \".csv,.json\"}}'\n```\n\nWhich maps to this JSON payload:\n```json\n{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\":         \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\",\n        \"output_path\":        \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\",\n        \"file_name\":          \"PROJECT_MAP\",\n        \"layout\":             \"vertical\",\n        \"max_depth\":          \"3\",\n        \"use_gitignore\":      \"true\",\n        \"ignored_path\":       \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Ftests, home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Fdocs\",\n        \"ignored_extensions\": \".csv,.json\"\n    }\n}\n```\n\nExpected output:\n```\n✅ Directory Structure Generated.\n   Path    : home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002FPROJECT_MAP.md\n   Layout  : vertical\n   Depth   : 3 levels\n   Lines   : 33\n   Size    : 986.0 B\n   Dirs    : 15\n   Files   : 26\n   Scanned : 282.2 KB\n```\n\n### ⚠️ IMPORTANT NOTES:\n- **All values in `tool_args` must be strings** (e.g. `\"max_depth\": \"3\"`, not `3`).\n- Common patterns (`.git`, `node_modules`, `__pycache__`, binaries, media) are auto-ignored.\n- If output exceeds 500 lines, a tip is shown to reduce `max_depth` or add `ignored_path`.\n- Default filename: `{dir_name}_structure.md` (e.g. `my-project_structure.md`).\n\n## Scenario-Based Instructions\n\n### 📁 Scenario 1: Small Project (\u003C 100 files)\n\n**When:** Scanning a small Python project, simple script, or personal library where we want to show almost everything, ignoring only cache and git files, using the default depth of 4.\n\n**What to ignore:** Minimal - only critical clutter\n- `__pycache__`, `.git`, `.venv`, `node_modules`\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-folder\",\n        \"ignored_path\": \"__pycache__, .git, .venv, .env, .gitkeep, .DS_Store, .log, .tmp\"\n    }\n}'\n```\n\n---\n\n### 📦 Scenario 2: Medium Web Application (100–1000 files)\n\n**When:** Scanning a typical React, Vue, or Node.js web app where we need to ignore dependencies and build outputs for a cleaner overview.\n\n**What to ignore:** Dependencies and build artifacts\n- `node_modules`, `dist`, `build`, `coverage`\n- `.next`, `.nuxt`, `.cache`\n- `__pycache__`, `.pytest_cache`\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-webapp\",\n        \"ignored_path\": \"node_modules, dist, .next, coverage, __pycache__, .git, .venv, .env, .gitkeep, .DS_Store, .log, .tmp\"\n    }\n}'\n```\n\n---\n\n### 🏢 Scenario 3: Large Codebase\u002FMonorepo (> 1000 files)\n\n**When:** Scanning an enterprise application, complex system, or a specific package within a large monorepo. We must ignore tests and dependencies to keep the output manageable.\n\n**Strategy:** \n1. **Never scan the entire root** - it will be too large\n2. **Target specific packages\u002Fmodules** one at a time\n3. **Use aggressive ignores**\n\n**What to ignore:** Everything non-essential\n- All dependencies: `node_modules`, `vendor`, `.venv`\n- All build outputs: `dist`, `build`, `out`, `target`\n- All test files and coverage\n- All media and assets\n\n**Example - Scan specific package:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmonorepo\u002Fpackages\u002Fbackend\",\n        \"ignored_path\": \"node_modules, dist, coverage, tests, __tests__, .git\"\n    }\n}'\n```\n\n**Example - Multiple targeted scans:**\n```bash\n# First: Backend\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmonorepo\u002Fpackages\u002Fbackend\",\n        \"output_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fdocs\",\n        \"ignored_path\": \"node_modules, dist, tests\"\n    }\n}'\n\n# Then: Frontend (separate call)\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmonorepo\u002Fpackages\u002Ffrontend\",\n        \"output_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fdocs\",\n        \"ignored_path\": \"node_modules, .next, public\u002Fassets\"\n    }\n}'\n```\n\n---\n\n### 🌍 Scenario 4: Root-Level Scan (home\u002Fuser_name\u002F or system root)\n\n**When:** Generating a system-wide or root workspace overview. We must aggressively ignore huge directories like workdir, chats, and knowledge to prevent overflowing the token limit.\n\n**⚠️ CRITICAL RULES:**\n1. **ALWAYS ignore these paths for home\u002Fuser_name\u002F:**\n   - `home\u002Fuser_name\u002Fworkdir` (user projects - scan separately)\n   - `home\u002Fuser_name\u002Fchats` (conversation history)\n   - `home\u002Fuser_name\u002Fknowledge\u002Fmain` (large knowledge base)\n   - `home\u002Fuser_name\u002Fmemory\u002Fdefault` (vector database)\n\n2. **What to show:**\n   - Agent configurations\n   - Skills\n   - System configuration files\n   - Project metadata\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002F\",\n        \"ignored_path\": \"home\u002Fuser_name\u002Fworkdir, home\u002Fuser_name\u002Fchats, home\u002Fuser_name\u002Fknowledge\u002Fmain, home\u002Fuser_name\u002Fmemory\u002Fdefault\"\n    }\n}'\n```\n\n---\n\n### 🎯 Scenario 5: Specific Folder Deep Dive\n\n**When:** The user requests a deep dive into ONE specific directory (e.g., \"show me the src folder structure\"). We need to show all source files with minimal filtering.\n\n**Strategy:**\n- Target ONLY that folder\n- Show everything inside (minimal ignores)\n- Good for code review, onboarding, documentation\n\n**What to ignore:** Only cache and temporary files\n- `__pycache__`, `.pytest_cache`\n- `*.pyc`, `.DS_Store`\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-app\u002Fsrc\",\n        \"ignored_path\": \"__pycache__, .pytest_cache\"\n    }\n}'\n```\n\n---\n\n### 📝 Scenario 6: Documentation Purpose\n\n**When:** Preparing structure output for a README, documentation, or architectural diagram. We should only show source code and configuration, strictly hiding test suites and build outputs.\n\n**Strategy:**\n- Focus on source code and configuration\n- Ignore everything that's not essential to understanding\n- Keep output clean and professional\n\n**What to ignore:**\n- All dependencies and node_modules\n- All build outputs and artifacts\n- All test files (unless specifically asked)\n- All media and binary files\n- All local development files (.env, .vscode)\n\n**Example:**\n```bash\nhuman-skills '{\n    \"tool_name\": \"tree_gen\",\n    \"tool_args\": {\n        \"input_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\",\n        \"output_path\": \"home\u002Fuser_name\u002Fworkdir\u002Fmy-project\u002Fdocs\",\n        \"ignored_path\": \"node_modules, dist, build, tests, __tests__, coverage, .git, .vscode, public\u002Fimages\"\n    }\n}'\n```\n\n---\n\n## Quick Reference: Common Ignore Patterns\n\n### By Language\u002FFramework\n\n**Python Projects:**\n```\n__pycache__, .pytest_cache, .venv, .mypy_cache, *.pyc, dist, build\n```\n\n**Node.js Projects:**\n```\nnode_modules, dist, build, .next, .nuxt, coverage, .cache\n```\n\n**Full-Stack Projects:**\n```\nnode_modules, __pycache__, dist, build, .venv, coverage, .git\n```\n\n### By Purpose\n\n**Code Review (show source only):**\n```\nnode_modules, dist, build, tests, __tests__, coverage, docs, public\n```\n\n**Documentation (clean view):**\n```\nnode_modules, dist, .git, .vscode, tests, coverage, *.min.js, assets\n```\n\n**Deployment Check (show build outputs):**\n```\nnode_modules, .git, src, tests (only ignore source and development files)\n```\n\n---\n\n## Best Practices\n\n### ✅ DO:\n1. **Always check project size first** - use `list_dir` to estimate\n2. **For large projects, scan specific directories** - never scan massive roots\n3. **For home\u002Fuser_name\u002F, ALWAYS ignore workdir and chats**\n4. **Match ignores to user's intent** - code review vs documentation needs different ignores\n5. **Present the output** - read structure.md and show it to user after generation\n\n### ❌ DON'T:\n1. **Don't scan home\u002Fuser_name\u002Fworkdir directly** - ask which project inside it\n2. **Don't forget node_modules** - it can have 100k+ files\n3. **Don't ignore too little** - output will be overwhelming\n4. **Don't use relative paths in ignored_path** - always use absolute paths\n5. **Don't generate without understanding user's goal** - ask if unclear\n\n---\n\n## Common Issues & Solutions\n\n| Issue | Solution |\n|-------|----------|\n| \"Output is 10,000+ lines\" | Add more aggressive ignores or target smaller directory |\n| \"Empty structure.md\" | Path doesn't exist or all files were ignored |\n| \"Still showing node_modules\" | Use absolute path: `\u002Ffull\u002Fpath\u002Fto\u002Fnode_modules` |\n| \"Missing important files\" | Review ignored_path - may have over-filtered |\n\n## Troubleshooting\n\n### Issue: Empty Output\n\n**Cause:** Directory doesn't exist or is empty.\n**Solution:** Verify the path exists with `list_dir` first.\n\n### Issue: Too Much Output\n\n**Cause:** Not enough ignore patterns.\n**Solution:** Add more paths\u002Fextensions to ignore, or generate subdirectories separately.\n\n### Issue: File Not Found\n\n**Cause:** Output directory doesn't exist.\n**Solution:** Create output directory first or use existing path.\n\n## Output Format\n\nThe generated `structure.md` file contains:\n- Markdown-formatted tree structure\n- File and folder counts\n- List of ignored paths\u002Fpatterns\n- Generation timestamp\n\nExample output:\n```markdown\n## file tree\n\u002Fmy-project\u002F\n├── src\u002F\n│   ├── main.py\n│   └── utils\u002F\n│       └── helpers.py\n├── tests\u002F\n│   └── test_main.py\n└── README.md\n```",{"name":5,"tags":49,"author":50,"version":51,"description":7,"trigger_patterns":52},[36,35,43,24,40],"Human Skill Team","1.0.0",[53,54,55,56,34,57,58,59],"directory structure","file tree","show structure","visualize folder","codebase tree","list files","dir structure","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Fmy_skills\u002Ftree_gen",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill tree_gen",{"tool":74,"command":75},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill tree_gen",{"tool":77,"command":78},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill tree_gen","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Ftree_gen\u002FSKILL.md",true,[82],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Ftree_gen.py","SCRIPT","脚本",18938,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Ftree_gen\u002Fscripts\u002Ftree_gen.py",[89,97,125,147,166,181],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"01M72JT3YP1SQHD0MANGDXQ4RT","higgsfield-websites","Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1\u002FR2\u002FKV\u002FDO\u002FContainers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references\u002Fwebsite-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references\u002Fapp-flow.md), `game` (realtime multiplayer rooms — references\u002Fgame-flow.md). Routes to the right flow; each carries its own rules and deploy\u002Fpublish gates.\nUse when: \"build me a website\", \"make a landing page\", \"create a web app\", \"build a SaaS dashboard \u002F portfolio\", \"make me a game\", \"deploy this site\", \"publish\". Also owns GAME ART: \"make a spritesheet\", \"tileable texture\", \"animate a 3D character\", game music\u002FSFX — see the game-* references.\nNOT for: single image\u002Fvideo\u002Faudio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fhiggsfield-ai_skills\u002Fhiggsfield-websites\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":115,"publishedAt":44},"01M70JPK8HAXXA85P7Q8NKZZYG","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-skills\u002FSKILL.md",[103,106,111,112],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":113,"categoryName":114,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[116,117,118,119,120,121,122,123,124],"writing","writing skills","editing","deployment","use","Existing","new","when","work",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":136,"publishedAt":44},"01M70JP4PHBH1CQVVDWZ94W159","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-plans\u002FSKILL.md",[131,132,133],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},{"categoryNo":134,"categoryName":135,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000030","开发工程师",[116,137,138,139,123,140,141,120,142,143,144,145,146],"writing plans","plans","you","code","for","requirements","task","multi","spec","multi-step task",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":44},"01M70JNTYVGXFZT8PASZ844TH8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fverification-before-completion\u002FSKILL.md",[],[154,155,156,157,158,159,120,160,161,162,123,163,124,164,165],"verification","verification before completion","complete","about","output","assertions","prs","evidence","claim","claims","commands","running",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":44},"01M70JNGVSQDESWN0Q5BPJ875V","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-superpowers\u002FSKILL.md",[172],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,175,176,177,120,123,178,179,180],"using superpowers","superpowers","conversation","how to","how","find","questions",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":44},"01M70JN57CE588NPYPYTWH1DWG","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-git-worktrees\u002FSKILL.md",[],[188,189,190,191,192,193,123,124,194,195,196,197,198,199,200,138,120,201,202],"using git worktrees","Using git","git","worktrees","git worktrees","implementation","git worktree","worktree","native","Tools","isolation","fallback","feature","via","workspace"]