[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CMM0NS1PDSYXT2C8SCKCR":3,"skill-same:01M73CMM0NS1PDSYXT2C8SCKCR":59},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M73CMM0NS1PDSYXT2C8SCKCR","tidy-project-structure",null,"Organize project files into conventional directories, update stale READMEs, clean configuration drift, and archive deprecated items without changing code logic. Use when files are scattered without clear organization, READMEs are outdated or contain broken examples, configuration files have multiplied across dev\u002Fstaging\u002Fprod, deprecated files remain in the project root, or naming conventions are inconsistent across directories.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftidy-project-structure\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: tidy-project-structure\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-05-03\"\ndescription: >\n  Organize project files into conventional directories, update stale READMEs,\n  clean configuration drift, and archive deprecated items without changing\n  code logic. Use when files are scattered without clear organization, READMEs\n  are outdated or contain broken examples, configuration files have multiplied\n  across dev\u002Fstaging\u002Fprod, deprecated files remain in the project root, or\n  naming conventions are inconsistent across directories.\nlicense: MIT\nallowed-tools: Read Write Edit Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: maintenance\n  complexity: intermediate\n  language: multi\n  tags: maintenance, organization, structure, readme, config\n---\n\n# tidy-project-structure\n\n## When to Use\n\nUse this skill when project organization has drifted from conventions:\n\n- Files scattered across directories without clear organization\n- READMEs are outdated or contain broken examples\n- Configuration files have multiplied (dev, staging, prod drift)\n- Deprecated files remain in project root\n- Naming conventions inconsistent across directories\n\n**Do NOT use** for code refactoring or dependency restructuring. This skill focuses on file organization and documentation hygiene.\n\n## Inputs\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `project_path` | string | Yes | Absolute path to project root |\n| `conventions` | string | No | Path to style guide (e.g., `docs\u002Fconventions.md`) |\n| `archive_mode` | enum | No | `move` (default) or `delete` for deprecated files |\n| `readme_update` | boolean | No | Update stale READMEs (default: true) |\n\n## Procedure\n\n### Step 1: Audit Directory Layout\n\nCompare current structure against project conventions or language best practices.\n\n**Common conventions by language**:\n\n**JavaScript\u002FTypeScript**:\n```\nsrc\u002F          # Source code\ntests\u002F        # Test files\ndist\u002F         # Build output (gitignored)\ndocs\u002F         # Documentation\n.github\u002F      # CI\u002FCD workflows\n```\n\n**Python**:\n```\npackage_name\u002F      # Package code\ntests\u002F             # Test suite\ndocs\u002F              # Sphinx docs\nscripts\u002F           # Utility scripts\n```\n\n**R**:\n```\nR\u002F                 # R source\ntests\u002Ftestthat\u002F    # Test suite\nman\u002F               # Documentation (generated)\nvignettes\u002F         # Long-form guides\ninst\u002F              # Installed files\ndata\u002F              # Package data\n```\n\n**Rust**:\n```\nsrc\u002F          # Source code\ntests\u002F        # Integration tests\nbenches\u002F      # Benchmarks\nexamples\u002F     # Usage examples\n```\n\n**Got:** List of files\u002Fdirectories violating conventions saved to `structure_audit.txt`\n\n**If fail:** If no conventions documented, use language-standard defaults\n\n### Step 2: Move Misplaced Files\n\nRelocate files to their conventional directories.\n\n**Common moves**:\n1. Test files outside `tests\u002F` → move to `tests\u002F`\n2. Documentation outside `docs\u002F` → move to `docs\u002F`\n3. Build artifacts in `src\u002F` → delete (should be gitignored)\n4. Config files in root → move to `config\u002F` or `.config\u002F`\n\nFor each move:\n```bash\n# Check if file is referenced anywhere\ngrep -r \"filename\" .\n\n# If no references or only relative path references:\nmkdir -p target_directory\u002F\ngit mv source\u002Ffile target_directory\u002Ffile\n\n# Update any imports\u002Frequires\n# (language-specific — see repair-broken-references skill)\n```\n\n**Got:** All files in conventional locations; git history preserved via `git mv`\n\n**If fail:** If moving breaks imports, update import paths or escalate\n\n### Step 3: Check README Freshness\n\nIdentify stale information in all README files.\n\n**Staleness indicators**:\n1. Last modified >6 months ago\n2. References to old version numbers\n3. Broken links or code examples\n4. Missing sections (Installation, Usage, Contributing)\n5. No license badge or broken badge links\n\n```bash\n# Find all READMEs\nfind . -name \"README.md\" -o -name \"readme.md\"\n\n# For each README:\n# - Check last modified date\ngit log -1 --format=\"%ci\" README.md\n\n# - Check for broken links\nmarkdown-link-check README.md\n\n# - Verify example code still runs (sample first example)\n```\n\n**Got:** List of stale READMEs in `readme_freshness.txt` with specific issues\n\n**If fail:** If markdown-link-check unavailable, manually review external links\n\n### Step 4: Update Stale READMEs\n\nFix broken links, update examples, add missing sections.\n\n**Standard fixes**:\n1. Replace broken badge URLs\n2. Update version numbers in installation instructions\n3. Fix broken example code (run to verify)\n4. Add missing sections (use template from project conventions)\n5. Update copyright year\n\n**README template structure**:\n```markdown\n# Project Name\n\nBrief description (1-2 sentences).\n\n## Installation\n\n```bash\n# Language-specific install command\n```\n\n## Usage\n\n```language\n# Basic example\n```\n\n## Documentation\n\nLink to full docs.\n\n## Contributing\n\nLink to CONTRIBUTING.md or inline guidelines.\n\n## License\n\nLICENSE badge and link.\n```\n\n**Got:** All READMEs updated; examples verified to run\n\n**If fail:** If example code cannot be verified, mark with warning comment\n\n### Step 5: Review Config Files\n\nIdentify configuration drift and consolidate duplicate settings.\n\n**Common config issues**:\n1. Multiple `.env` files (`.env`, `.env.local`, `.env.dev`, `.env.prod`)\n2. Duplicate settings across config files\n3. Hardcoded secrets (should use environment variables)\n4. Outdated API endpoints or feature flags\n\n```bash\n# Find all config files\nfind . -name \"*.config.*\" -o -name \".env*\" -o -name \"*.yml\" -o -name \"*.yaml\"\n\n# For each config:\n# - Check for duplicate keys\n# - Grep for hardcoded secrets (API keys, tokens, passwords)\ngrep -E \"(api[_-]?key|token|password|secret)\" config_file\n\n# - Compare dev vs prod settings\ndiff .env.dev .env.prod\n```\n\n**Got:** Config drift documented in `config_review.txt`; secrets flagged for escalation\n\n**If fail:** If diff shows major divergence, escalate to devops-engineer\n\n### Step 6: Archive Deprecated Files\n\nMove or delete files no longer needed.\n\n**Candidates for archiving**:\n- Commented-out config files (e.g., `nginx.conf.old`)\n- Legacy scripts not run in >1 year\n- Backup files (e.g., `file.bak`, `file~`)\n- Build artifacts accidentally committed\n\n**Archive process**:\n```bash\n# Create archive directory (if archive_mode=move)\nmkdir -p archive\u002FYYYY-MM-DD\u002F\n\n# For each deprecated file:\n# 1. Verify not referenced anywhere\ngrep -r \"filename\" .\n\n# 2. Check git history for last modification\ngit log -1 --format=\"%ci\" filename\n\n# 3. If not modified in >1 year and no references:\nif [ \"$archive_mode\" = \"move\" ]; then\n  git mv filename archive\u002FYYYY-MM-DD\u002F\nelse\n  git rm filename\nfi\n\n# 4. Document in ARCHIVE_LOG.md\necho \"- filename (reason, last modified: DATE)\" >> ARCHIVE_LOG.md\n```\n\n**Got:** Deprecated files archived; `ARCHIVE_LOG.md` updated\n\n**If fail:** If uncertain whether file is deprecated, leave in place and document in report\n\n### Step 7: Verify Naming Conventions\n\nCheck for inconsistent file naming across project.\n\n**Common conventions**:\n- **kebab-case**: `my-file.js` (common in JS\u002Fweb projects)\n- **snake_case**: `my_file.py` (Python standard)\n- **PascalCase**: `MyComponent.tsx` (React components)\n- **camelCase**: `myUtility.js` (JavaScript functions)\n\n```bash\n# Find files violating conventions\n# Example: Python project expecting snake_case\nfind . -name \"*.py\" | grep -v \"__pycache__\" | grep -E \"[A-Z-]\"\n\n# For each violation, either:\n# 1. Rename to match conventions\n# 2. Document exception (e.g., Django settings.py convention)\n```\n\n**Got:** All files follow naming conventions or exceptions documented\n\n**If fail:** If renaming breaks imports, update references or escalate\n\n### Step 8: Generate Tidying Report\n\nDocument all structural changes.\n\n```markdown\n# Project Structure Tidying Report\n\n**Date**: YYYY-MM-DD\n**Project**: \u003Cproject_name>\n\n## Directory Changes\n\n- Moved X files to conventional directories\n- Created Y new directories\n- Archived Z deprecated files\n\n## README Updates\n\n- Updated W stale READMEs\n- Fixed X broken links\n- Verified Y code examples\n\n## Config Cleanup\n\n- Consolidated X duplicate settings\n- Flagged Y hardcoded secrets for removal\n- Documented Z config drift issues\n\n## Files Archived\n\nSee ARCHIVE_LOG.md for full list (Z files).\n\n## Naming Convention Fixes\n\n- Renamed X files to match conventions\n- Documented Y exceptions\n\n## Escalations\n\n- [Config drift requiring devops review]\n- [Hardcoded secrets requiring security audit]\n```\n\n**Got:** Report saved to `TIDYING_REPORT.md`\n\n**If fail:** (N\u002FA — generate report regardless)\n\n## Validation Checklist\n\nAfter tidying:\n\n- [ ] All files in conventional directories\n- [ ] No broken links in any README\n- [ ] README examples verified to run\n- [ ] Config files reviewed for secrets\n- [ ] Deprecated files archived with documentation\n- [ ] Naming conventions consistent\n- [ ] Git history preserved (used `git mv`, not `mv`)\n- [ ] Tests still pass after moves\n\n## Pitfalls\n\n1. **Breaking Relative Imports**: Moving files breaks relative import paths. Update all references or use absolute imports.\n\n2. **Losing Git History**: Using `mv` instead of `git mv` loses file history. Always use git commands for moves.\n\n3. **Over-Organizing**: Creating too many nested directories makes navigation harder. Keep it flat until complexity requires structure.\n\n4. **Deleting Instead of Archiving**: Direct deletion loses ability to recover. Always archive first unless certain.\n\n5. **Ignoring Language Conventions**: Imposing personal preferences over language standards. Follow established conventions.\n\n6. **Not Updating Documentation**: Moving files without updating README paths leaves docs broken.\n\n## Related Skills\n\n- [clean-codebase](..\u002Fclean-codebase\u002FSKILL.md) — Remove dead code, fix lint warnings\n- [repair-broken-references](..\u002Frepair-broken-references\u002FSKILL.md) — Fix links and imports after moves\n- [escalate-issues](..\u002Fescalate-issues\u002FSKILL.md) — Route complex config issues to specialists\n- [devops\u002Fconfig-management](..\u002F..\u002Fdevops\u002Fconfig-management\u002FSKILL.md) — Advanced config consolidation\n- [compliance\u002Fdocumentation-audit](..\u002F..\u002Fcompliance\u002Fdocumentation-audit\u002FSKILL.md) — Comprehensive doc review\n","# tidy-project-structure\n\n## When to Use\n\nUse this skill when project organization has drifted from conventions:\n\n- Files scattered across directories without clear organization\n- READMEs are outdated or contain broken examples\n- Configuration files have multiplied (dev, staging, prod drift)\n- Deprecated files remain in project root\n- Naming conventions inconsistent across directories\n\n**Do NOT use** for code refactoring or dependency restructuring. This skill focuses on file organization and documentation hygiene.\n\n## Inputs\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| `project_path` | string | Yes | Absolute path to project root |\n| `conventions` | string | No | Path to style guide (e.g., `docs\u002Fconventions.md`) |\n| `archive_mode` | enum | No | `move` (default) or `delete` for deprecated files |\n| `readme_update` | boolean | No | Update stale READMEs (default: true) |\n\n## Procedure\n\n### Step 1: Audit Directory Layout\n\nCompare current structure against project conventions or language best practices.\n\n**Common conventions by language**:\n\n**JavaScript\u002FTypeScript**:\n```\nsrc\u002F          # Source code\ntests\u002F        # Test files\ndist\u002F         # Build output (gitignored)\ndocs\u002F         # Documentation\n.github\u002F      # CI\u002FCD workflows\n```\n\n**Python**:\n```\npackage_name\u002F      # Package code\ntests\u002F             # Test suite\ndocs\u002F              # Sphinx docs\nscripts\u002F           # Utility scripts\n```\n\n**R**:\n```\nR\u002F                 # R source\ntests\u002Ftestthat\u002F    # Test suite\nman\u002F               # Documentation (generated)\nvignettes\u002F         # Long-form guides\ninst\u002F              # Installed files\ndata\u002F              # Package data\n```\n\n**Rust**:\n```\nsrc\u002F          # Source code\ntests\u002F        # Integration tests\nbenches\u002F      # Benchmarks\nexamples\u002F     # Usage examples\n```\n\n**Got:** List of files\u002Fdirectories violating conventions saved to `structure_audit.txt`\n\n**If fail:** If no conventions documented, use language-standard defaults\n\n### Step 2: Move Misplaced Files\n\nRelocate files to their conventional directories.\n\n**Common moves**:\n1. Test files outside `tests\u002F` → move to `tests\u002F`\n2. Documentation outside `docs\u002F` → move to `docs\u002F`\n3. Build artifacts in `src\u002F` → delete (should be gitignored)\n4. Config files in root → move to `config\u002F` or `.config\u002F`\n\nFor each move:\n```bash\n# Check if file is referenced anywhere\ngrep -r \"filename\" .\n\n# If no references or only relative path references:\nmkdir -p target_directory\u002F\ngit mv source\u002Ffile target_directory\u002Ffile\n\n# Update any imports\u002Frequires\n# (language-specific — see repair-broken-references skill)\n```\n\n**Got:** All files in conventional locations; git history preserved via `git mv`\n\n**If fail:** If moving breaks imports, update import paths or escalate\n\n### Step 3: Check README Freshness\n\nIdentify stale information in all README files.\n\n**Staleness indicators**:\n1. Last modified >6 months ago\n2. References to old version numbers\n3. Broken links or code examples\n4. Missing sections (Installation, Usage, Contributing)\n5. No license badge or broken badge links\n\n```bash\n# Find all READMEs\nfind . -name \"README.md\" -o -name \"readme.md\"\n\n# For each README:\n# - Check last modified date\ngit log -1 --format=\"%ci\" README.md\n\n# - Check for broken links\nmarkdown-link-check README.md\n\n# - Verify example code still runs (sample first example)\n```\n\n**Got:** List of stale READMEs in `readme_freshness.txt` with specific issues\n\n**If fail:** If markdown-link-check unavailable, manually review external links\n\n### Step 4: Update Stale READMEs\n\nFix broken links, update examples, add missing sections.\n\n**Standard fixes**:\n1. Replace broken badge URLs\n2. Update version numbers in installation instructions\n3. Fix broken example code (run to verify)\n4. Add missing sections (use template from project conventions)\n5. Update copyright year\n\n**README template structure**:\n```markdown\n# Project Name\n\nBrief description (1-2 sentences).\n\n## Installation\n\n```bash\n# Language-specific install command\n```\n\n## Usage\n\n```language\n# Basic example\n```\n\n## Documentation\n\nLink to full docs.\n\n## Contributing\n\nLink to CONTRIBUTING.md or inline guidelines.\n\n## License\n\nLICENSE badge and link.\n```\n\n**Got:** All READMEs updated; examples verified to run\n\n**If fail:** If example code cannot be verified, mark with warning comment\n\n### Step 5: Review Config Files\n\nIdentify configuration drift and consolidate duplicate settings.\n\n**Common config issues**:\n1. Multiple `.env` files (`.env`, `.env.local`, `.env.dev`, `.env.prod`)\n2. Duplicate settings across config files\n3. Hardcoded secrets (should use environment variables)\n4. Outdated API endpoints or feature flags\n\n```bash\n# Find all config files\nfind . -name \"*.config.*\" -o -name \".env*\" -o -name \"*.yml\" -o -name \"*.yaml\"\n\n# For each config:\n# - Check for duplicate keys\n# - Grep for hardcoded secrets (API keys, tokens, passwords)\ngrep -E \"(api[_-]?key|token|password|secret)\" config_file\n\n# - Compare dev vs prod settings\ndiff .env.dev .env.prod\n```\n\n**Got:** Config drift documented in `config_review.txt`; secrets flagged for escalation\n\n**If fail:** If diff shows major divergence, escalate to devops-engineer\n\n### Step 6: Archive Deprecated Files\n\nMove or delete files no longer needed.\n\n**Candidates for archiving**:\n- Commented-out config files (e.g., `nginx.conf.old`)\n- Legacy scripts not run in >1 year\n- Backup files (e.g., `file.bak`, `file~`)\n- Build artifacts accidentally committed\n\n**Archive process**:\n```bash\n# Create archive directory (if archive_mode=move)\nmkdir -p archive\u002FYYYY-MM-DD\u002F\n\n# For each deprecated file:\n# 1. Verify not referenced anywhere\ngrep -r \"filename\" .\n\n# 2. Check git history for last modification\ngit log -1 --format=\"%ci\" filename\n\n# 3. If not modified in >1 year and no references:\nif [ \"$archive_mode\" = \"move\" ]; then\n  git mv filename archive\u002FYYYY-MM-DD\u002F\nelse\n  git rm filename\nfi\n\n# 4. Document in ARCHIVE_LOG.md\necho \"- filename (reason, last modified: DATE)\" >> ARCHIVE_LOG.md\n```\n\n**Got:** Deprecated files archived; `ARCHIVE_LOG.md` updated\n\n**If fail:** If uncertain whether file is deprecated, leave in place and document in report\n\n### Step 7: Verify Naming Conventions\n\nCheck for inconsistent file naming across project.\n\n**Common conventions**:\n- **kebab-case**: `my-file.js` (common in JS\u002Fweb projects)\n- **snake_case**: `my_file.py` (Python standard)\n- **PascalCase**: `MyComponent.tsx` (React components)\n- **camelCase**: `myUtility.js` (JavaScript functions)\n\n```bash\n# Find files violating conventions\n# Example: Python project expecting snake_case\nfind . -name \"*.py\" | grep -v \"__pycache__\" | grep -E \"[A-Z-]\"\n\n# For each violation, either:\n# 1. Rename to match conventions\n# 2. Document exception (e.g., Django settings.py convention)\n```\n\n**Got:** All files follow naming conventions or exceptions documented\n\n**If fail:** If renaming breaks imports, update references or escalate\n\n### Step 8: Generate Tidying Report\n\nDocument all structural changes.\n\n```markdown\n# Project Structure Tidying Report\n\n**Date**: YYYY-MM-DD\n**Project**: \u003Cproject_name>\n\n## Directory Changes\n\n- Moved X files to conventional directories\n- Created Y new directories\n- Archived Z deprecated files\n\n## README Updates\n\n- Updated W stale READMEs\n- Fixed X broken links\n- Verified Y code examples\n\n## Config Cleanup\n\n- Consolidated X duplicate settings\n- Flagged Y hardcoded secrets for removal\n- Documented Z config drift issues\n\n## Files Archived\n\nSee ARCHIVE_LOG.md for full list (Z files).\n\n## Naming Convention Fixes\n\n- Renamed X files to match conventions\n- Documented Y exceptions\n\n## Escalations\n\n- [Config drift requiring devops review]\n- [Hardcoded secrets requiring security audit]\n```\n\n**Got:** Report saved to `TIDYING_REPORT.md`\n\n**If fail:** (N\u002FA — generate report regardless)\n\n## Validation Checklist\n\nAfter tidying:\n\n- [ ] All files in conventional directories\n- [ ] No broken links in any README\n- [ ] README examples verified to run\n- [ ] Config files reviewed for secrets\n- [ ] Deprecated files archived with documentation\n- [ ] Naming conventions consistent\n- [ ] Git history preserved (used `git mv`, not `mv`)\n- [ ] Tests still pass after moves\n\n## Pitfalls\n\n1. **Breaking Relative Imports**: Moving files breaks relative import paths. Update all references or use absolute imports.\n\n2. **Losing Git History**: Using `mv` instead of `git mv` loses file history. Always use git commands for moves.\n\n3. **Over-Organizing**: Creating too many nested directories makes navigation harder. Keep it flat until complexity requires structure.\n\n4. **Deleting Instead of Archiving**: Direct deletion loses ability to recover. Always archive first unless certain.\n\n5. **Ignoring Language Conventions**: Imposing personal preferences over language standards. Follow established conventions.\n\n6. **Not Updating Documentation**: Moving files without updating README paths leaves docs broken.\n\n## Related Skills\n\n- [clean-codebase](..\u002Fclean-codebase\u002FSKILL.md) — Remove dead code, fix lint warnings\n- [repair-broken-references](..\u002Frepair-broken-references\u002FSKILL.md) — Fix links and imports after moves\n- [escalate-issues](..\u002Fescalate-issues\u002FSKILL.md) — Route complex config issues to specialists\n- [devops\u002Fconfig-management](..\u002F..\u002Fdevops\u002Fconfig-management\u002FSKILL.md) — Advanced config consolidation\n- [compliance\u002Fdocumentation-audit](..\u002F..\u002Fcompliance\u002Fdocumentation-audit\u002FSKILL.md) — Comprehensive doc review\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"maintenance, organization, structure, readme, config","Philipp Thoss","maintenance","1.0","multi","intermediate","Julius Brussee homage — caveman","Organize project files into conventional directories, update stale READMEs, clean configuration drift, and archive deprecated items without changing code logic. Use when files are scattered without clear organization, READMEs are outdated or contain broken examples, configuration files have multiplied across dev\u002Fstaging\u002Fprod, deprecated files remain in the project root, or naming conventions are inconsistent across directories.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-05-03","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Ftidy-project-structure",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill tidy-project-structure",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill tidy-project-structure",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill tidy-project-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftidy-project-structure\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"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":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]