[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF6H4TS06ZRMBMREHVNWM0":3,"skill-same:01M6AF6H4TS06ZRMBMREHVNWM0":80},{"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":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6AF6H4TS06ZRMBMREHVNWM0","file-organizer",null,"Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Ffile-organizer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"file","file organizer","downloads","projects","context","user","remove","use","up","duplicates","files","clean","organize","directories","organize downloads","when","2026-11-10 10:12:30",false,"---\nname: file-organizer\ndescription: Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects.\n---\n\n# File Organizer\n\n## When to Use This Skill\n\n- Your Downloads folder is a chaotic mess\n- You can't find files because they're scattered everywhere\n- You have duplicate files taking up space\n- Your folder structure doesn't make sense anymore\n- You want to establish better organization habits\n- You're starting a new project and need a good structure\n- You're cleaning up before archiving old projects\n\n## What This Skill Does\n\n1. **Analyzes Current Structure**: Reviews your folders and files to understand what you have\n2. **Finds Duplicates**: Identifies duplicate files across your system\n3. **Suggests Organization**: Proposes logical folder structures based on your content\n4. **Automates Cleanup**: Moves, renames, and organizes files with your approval\n5. **Maintains Context**: Makes smart decisions based on file types, dates, and content\n6. **Reduces Clutter**: Identifies old files you probably don't need anymore\n\n## Instructions\n\nWhen a user requests file organization help:\n\n1. **Understand the Scope**\n\n   Ask clarifying questions:\n\n   - Which directory needs organization? (Downloads, Documents, entire home folder?)\n   - What's the main problem? (Can't find things, duplicates, too messy, no structure?)\n   - Any files or folders to avoid? (Current projects, sensitive data?)\n   - How aggressively to organize? (Conservative vs. comprehensive cleanup)\n\n2. **Analyze Current State**\n\n   Review the target directory:\n\n   ```bash\n   # Get overview of current structure\n   ls -la [target_directory]\n\n   # Check file types and sizes\n   find [target_directory] -type f -exec file {} \\; | head -20\n\n   # Identify largest files\n   du -sh [target_directory]\u002F* | sort -rh | head -20\n\n   # Count file types\n   find [target_directory] -type f | sed 's\u002F.*\\.\u002F\u002F' | sort | uniq -c | sort -rn\n   ```\n\n   Summarize findings:\n\n   - Total files and folders\n   - File type breakdown\n   - Size distribution\n   - Date ranges\n   - Obvious organization issues\n\n3. **Identify Organization Patterns**\n\n   Based on the files, determine logical groupings:\n\n   **By Type**:\n\n   - Documents (PDFs, DOCX, TXT)\n   - Images (JPG, PNG, SVG)\n   - Videos (MP4, MOV)\n   - Archives (ZIP, TAR, DMG)\n   - Code\u002FProjects (directories with code)\n   - Spreadsheets (XLSX, CSV)\n   - Presentations (PPTX, KEY)\n\n   **By Purpose**:\n\n   - Work vs. Personal\n   - Active vs. Archive\n   - Project-specific\n   - Reference materials\n   - Temporary\u002Fscratch files\n\n   **By Date**:\n\n   - Current year\u002Fmonth\n   - Previous years\n   - Very old (archive candidates)\n\n4. **Find Duplicates**\n\n   When requested, search for duplicates:\n\n   ```bash\n   # Find exact duplicates by hash\n   find [directory] -type f -exec md5 {} \\; | sort | uniq -d\n\n   # Find files with similar names\n   find [directory] -type f -printf '%f\\n' | sort | uniq -d\n\n   # Find similar-sized files\n   find [directory] -type f -printf '%s %p\\n' | sort -n\n   ```\n\n   For each set of duplicates:\n\n   - Show all file paths\n   - Display sizes and modification dates\n   - Recommend which to keep (usually newest or best-named)\n   - **Important**: Always ask for confirmation before deleting\n\n5. **Propose Organization Plan**\n\n   Present a clear plan before making changes:\n\n   ```markdown\n   # Organization Plan for [Directory]\n\n   ## Current State\n\n   - X files across Y folders\n   - [Size] total\n   - File types: [breakdown]\n   - Issues: [list problems]\n\n   ## Proposed Structure\n\n   [Directory]\u002F\n   ├── Work\u002F\n   │ ├── Projects\u002F\n   │ ├── Documents\u002F\n   │ └── Archive\u002F\n   ├── Personal\u002F\n   │ ├── Photos\u002F\n   │ ├── Documents\u002F\n   │ └── Media\u002F\n   └── Downloads\u002F\n   ├── To-Sort\u002F\n   └── Archive\u002F\n\n   ## Changes I'll Make\n\n   1. **Create new folders**: [list]\n   2. **Move files**:\n      - X PDFs → Work\u002FDocuments\u002F\n      - Y images → Personal\u002FPhotos\u002F\n      - Z old files → Archive\u002F\n   3. **Rename files**: [any renaming patterns]\n   4. **Delete**: [duplicates or trash files]\n\n   ## Files Needing Your Decision\n\n   - [List any files you're unsure about]\n\n   Ready to proceed? (yes\u002Fno\u002Fmodify)\n   ```\n\n6. **Execute Organization**\n\n   After approval, organize systematically:\n\n   ```bash\n   # Create folder structure\n   mkdir -p \"path\u002Fto\u002Fnew\u002Ffolders\"\n\n   # Move files with clear logging\n   mv \"old\u002Fpath\u002Ffile.pdf\" \"new\u002Fpath\u002Ffile.pdf\"\n\n   # Rename files with consistent patterns\n   # Example: \"YYYY-MM-DD - Description.ext\"\n   ```\n\n   **Important Rules**:\n\n   - Always confirm before deleting anything\n   - Log all moves for potential undo\n   - Preserve original modification dates\n   - Handle filename conflicts gracefully\n   - Stop and ask if you encounter unexpected situations\n\n7. **Provide Summary and Maintenance Tips**\n\n   After organizing:\n\n   ```markdown\n   # Organization Complete! ✨\n\n   ## What Changed\n\n   - Created [X] new folders\n   - Organized [Y] files\n   - Freed [Z] GB by removing duplicates\n   - Archived [W] old files\n\n   ## New Structure\n\n   [Show the new folder tree]\n\n   ## Maintenance Tips\n\n   To keep this organized:\n\n   1. **Weekly**: Sort new downloads\n   2. **Monthly**: Review and archive completed projects\n   3. **Quarterly**: Check for new duplicates\n   4. **Yearly**: Archive old files\n\n   ## Quick Commands for You\n\n   # Find files modified this week\n\n   find . -type f -mtime -7\n\n   # Sort downloads by type\n\n   [custom command for their setup]\n\n   # Find duplicates\n\n   [custom command]\n   ```\n\n   Want to organize another folder?\n\n## Best Practices\n\n### Folder Naming\n\n- Use clear, descriptive names\n- Avoid spaces (use hyphens or underscores)\n- Be specific: \"client-proposals\" not \"docs\"\n- Use prefixes for ordering: \"01-current\", \"02-archive\"\n\n### File Naming\n\n- Include dates: \"2024-10-17-meeting-notes.md\"\n- Be descriptive: \"q3-financial-report.xlsx\"\n- Avoid version numbers in names (use version control instead)\n- Remove download artifacts: \"document-final-v2 (1).pdf\" → \"document.pdf\"\n\n### When to Archive\n\n- Projects not touched in 6+ months\n- Completed work that might be referenced later\n- Old versions after migration to new systems\n- Files you're hesitant to delete (archive first)\n","# File Organizer\n\n## When to Use This Skill\n\n- Your Downloads folder is a chaotic mess\n- You can't find files because they're scattered everywhere\n- You have duplicate files taking up space\n- Your folder structure doesn't make sense anymore\n- You want to establish better organization habits\n- You're starting a new project and need a good structure\n- You're cleaning up before archiving old projects\n\n## What This Skill Does\n\n1. **Analyzes Current Structure**: Reviews your folders and files to understand what you have\n2. **Finds Duplicates**: Identifies duplicate files across your system\n3. **Suggests Organization**: Proposes logical folder structures based on your content\n4. **Automates Cleanup**: Moves, renames, and organizes files with your approval\n5. **Maintains Context**: Makes smart decisions based on file types, dates, and content\n6. **Reduces Clutter**: Identifies old files you probably don't need anymore\n\n## Instructions\n\nWhen a user requests file organization help:\n\n1. **Understand the Scope**\n\n   Ask clarifying questions:\n\n   - Which directory needs organization? (Downloads, Documents, entire home folder?)\n   - What's the main problem? (Can't find things, duplicates, too messy, no structure?)\n   - Any files or folders to avoid? (Current projects, sensitive data?)\n   - How aggressively to organize? (Conservative vs. comprehensive cleanup)\n\n2. **Analyze Current State**\n\n   Review the target directory:\n\n   ```bash\n   # Get overview of current structure\n   ls -la [target_directory]\n\n   # Check file types and sizes\n   find [target_directory] -type f -exec file {} \\; | head -20\n\n   # Identify largest files\n   du -sh [target_directory]\u002F* | sort -rh | head -20\n\n   # Count file types\n   find [target_directory] -type f | sed 's\u002F.*\\.\u002F\u002F' | sort | uniq -c | sort -rn\n   ```\n\n   Summarize findings:\n\n   - Total files and folders\n   - File type breakdown\n   - Size distribution\n   - Date ranges\n   - Obvious organization issues\n\n3. **Identify Organization Patterns**\n\n   Based on the files, determine logical groupings:\n\n   **By Type**:\n\n   - Documents (PDFs, DOCX, TXT)\n   - Images (JPG, PNG, SVG)\n   - Videos (MP4, MOV)\n   - Archives (ZIP, TAR, DMG)\n   - Code\u002FProjects (directories with code)\n   - Spreadsheets (XLSX, CSV)\n   - Presentations (PPTX, KEY)\n\n   **By Purpose**:\n\n   - Work vs. Personal\n   - Active vs. Archive\n   - Project-specific\n   - Reference materials\n   - Temporary\u002Fscratch files\n\n   **By Date**:\n\n   - Current year\u002Fmonth\n   - Previous years\n   - Very old (archive candidates)\n\n4. **Find Duplicates**\n\n   When requested, search for duplicates:\n\n   ```bash\n   # Find exact duplicates by hash\n   find [directory] -type f -exec md5 {} \\; | sort | uniq -d\n\n   # Find files with similar names\n   find [directory] -type f -printf '%f\\n' | sort | uniq -d\n\n   # Find similar-sized files\n   find [directory] -type f -printf '%s %p\\n' | sort -n\n   ```\n\n   For each set of duplicates:\n\n   - Show all file paths\n   - Display sizes and modification dates\n   - Recommend which to keep (usually newest or best-named)\n   - **Important**: Always ask for confirmation before deleting\n\n5. **Propose Organization Plan**\n\n   Present a clear plan before making changes:\n\n   ```markdown\n   # Organization Plan for [Directory]\n\n   ## Current State\n\n   - X files across Y folders\n   - [Size] total\n   - File types: [breakdown]\n   - Issues: [list problems]\n\n   ## Proposed Structure\n\n   [Directory]\u002F\n   ├── Work\u002F\n   │ ├── Projects\u002F\n   │ ├── Documents\u002F\n   │ └── Archive\u002F\n   ├── Personal\u002F\n   │ ├── Photos\u002F\n   │ ├── Documents\u002F\n   │ └── Media\u002F\n   └── Downloads\u002F\n   ├── To-Sort\u002F\n   └── Archive\u002F\n\n   ## Changes I'll Make\n\n   1. **Create new folders**: [list]\n   2. **Move files**:\n      - X PDFs → Work\u002FDocuments\u002F\n      - Y images → Personal\u002FPhotos\u002F\n      - Z old files → Archive\u002F\n   3. **Rename files**: [any renaming patterns]\n   4. **Delete**: [duplicates or trash files]\n\n   ## Files Needing Your Decision\n\n   - [List any files you're unsure about]\n\n   Ready to proceed? (yes\u002Fno\u002Fmodify)\n   ```\n\n6. **Execute Organization**\n\n   After approval, organize systematically:\n\n   ```bash\n   # Create folder structure\n   mkdir -p \"path\u002Fto\u002Fnew\u002Ffolders\"\n\n   # Move files with clear logging\n   mv \"old\u002Fpath\u002Ffile.pdf\" \"new\u002Fpath\u002Ffile.pdf\"\n\n   # Rename files with consistent patterns\n   # Example: \"YYYY-MM-DD - Description.ext\"\n   ```\n\n   **Important Rules**:\n\n   - Always confirm before deleting anything\n   - Log all moves for potential undo\n   - Preserve original modification dates\n   - Handle filename conflicts gracefully\n   - Stop and ask if you encounter unexpected situations\n\n7. **Provide Summary and Maintenance Tips**\n\n   After organizing:\n\n   ```markdown\n   # Organization Complete! ✨\n\n   ## What Changed\n\n   - Created [X] new folders\n   - Organized [Y] files\n   - Freed [Z] GB by removing duplicates\n   - Archived [W] old files\n\n   ## New Structure\n\n   [Show the new folder tree]\n\n   ## Maintenance Tips\n\n   To keep this organized:\n\n   1. **Weekly**: Sort new downloads\n   2. **Monthly**: Review and archive completed projects\n   3. **Quarterly**: Check for new duplicates\n   4. **Yearly**: Archive old files\n\n   ## Quick Commands for You\n\n   # Find files modified this week\n\n   find . -type f -mtime -7\n\n   # Sort downloads by type\n\n   [custom command for their setup]\n\n   # Find duplicates\n\n   [custom command]\n   ```\n\n   Want to organize another folder?\n\n## Best Practices\n\n### Folder Naming\n\n- Use clear, descriptive names\n- Avoid spaces (use hyphens or underscores)\n- Be specific: \"client-proposals\" not \"docs\"\n- Use prefixes for ordering: \"01-current\", \"02-archive\"\n\n### File Naming\n\n- Include dates: \"2024-10-17-meeting-notes.md\"\n- Be descriptive: \"q3-financial-report.xlsx\"\n- Avoid version numbers in names (use version control instead)\n- Remove download artifacts: \"document-final-v2 (1).pdf\" → \"document.pdf\"\n\n### When to Archive\n\n- Projects not touched in 6+ months\n- Completed work that might be referenced later\n- Old versions after migration to new systems\n- Files you're hesitant to delete (archive first)\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Ffile-organizer",3911,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-11 21:38:31",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add davila7\u002Fclaude-code-templates --skill file-organizer",{"tool":56,"command":57},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill file-organizer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill file-organizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Ffile-organizer\u002FSKILL.md",true,[64,70,76],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fprd_templates.md","REFERENCE","参考文档",7249,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Freferences\u002Fprd_templates.md",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Fcustomer_interview_analyzer.py","SCRIPT","脚本",17066,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Fcustomer_interview_analyzer.py",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Frice_prioritizer.py",11872,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Falirezarezvani-claude-skills\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py",[81,111,138,171,205,229],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":35},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[93,94,95,96,97,98,99,100,26,34,101,102,103,104,105,106,107,108,109,110],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"publishedAt":35},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[117],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[119,120,121,122,123,124,125,126,127,128,129,34,130,131,132,133,134,135,136,137],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":153,"publishedAt":35},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[144,147,148],{"categoryNo":145,"categoryName":146,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[154,155,156,157,158,159,160,98,161,162,163,164,165,166,167,26,168,169,34,170],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":176,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":35},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000009","前端开发",[183,184,185,186,187,188,189,190,191,192,193,194,195,19,196,197,198,199,200,201,202,203,98,204],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":209,"sourceHtmlUrl":210,"categories":211,"keywords":216,"publishedAt":35},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[212,215],{"categoryNo":213,"categoryName":214,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":180,"categoryName":181,"taxonomyType":90,"taxonomyTypeDesc":91},[217,218,219,220,221,184,222,193,194,223,224,225,226,98,227,102,228],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":175,"licenseFileUrl":233,"sourceHtmlUrl":234,"categories":235,"keywords":243,"publishedAt":35},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[236,239,240],{"categoryNo":237,"categoryName":238,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":241,"categoryName":242,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000036","内容创作者",[244,245,246,247,248,249,250,251,186,252,19,130,253,254,255,256,27,166,257,34,258,259,260,261,262,108,263],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","invoke","you","analysis","claims","argument","assemble","recommendations"]