[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN11SMPBSMF3Y0QK7PXFFC":3,"skill-same:01M7EN11SMPBSMF3Y0QK7PXFFC":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EN11SMPBSMF3Y0QK7PXFFC","ams-file-organizer",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-file-organizer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: file-organizer\ndescription: Organize files so you can find anything: naming conventions, folder structures, archiving, and deduplication. Use when digital clutter slows you down or you're setting up a new system.\ncategory: productivity\n---\n\n# File Organizer\n\n## Overview\n\nFile chaos has a cost: every search, every 'final_v2_REAL' confusion, every duplicated download burns time and trust.\n\nA working system: consistent naming, shallow meaningful folders, an inbox for unsorted files, and regular archiving.\n\nGoal: any file findable in 30 seconds via search or two folder clicks — months later, by future you.\n\n## When to use\n\n- Downloads folder with thousands of unsorted files\n- Setting up file organization on a new computer\n- 'final_v2_FINAL' version chaos in shared projects\n- Photo\u002Fdocument libraries growing unmanageable\n- Teams needing shared file conventions\n\n## Core concepts\n\n- **Naming conventions.**\n  `YYYY-MM-DD descriptive-name v03.ext`. Dates sort chronologically; descriptive names are searchable; versions are explicit. Agree once, use always.\n- **Shallow folders.**\n  2-3 levels deep max. Deep trees hide files; search + good names beat elaborate hierarchies.\n- **The inbox pattern.**\n  One `00 Inbox` folder for all new\u002Funsorted files. Process weekly: file, rename, or delete. Never browse the inbox as storage.\n- **PARA or project structure.**\n  Top level by actionability (Projects\u002FAreas\u002FResources\u002FArchive) or by project. Pick one; apply everywhere.\n- **Versioning discipline.**\n  Explicit versions (`v01`, `v02`) or version control (git) for documents. Never 'final', 'final2', 'final-FINAL'.\n- **Deduplication.**\n  Periodic sweeps for duplicates (same file, three locations). Hash-based tools find them reliably; keep one canonical copy.\n- **Archive vs. delete.**\n  Archive completed\u002Fold work (cheap storage); delete true junk (duplicates, installers, temp files). Archiving everything = hoarding.\n- **Search-first retrieval.**\n  Good names + OS search\u002Findexing. Train yourself to search rather than browse — it's faster once names are consistent.\n\n## Practical workflow\n\n1. **Audit the mess.**\n   Survey: where are files now, what's duplicated, what's the inbox situation. Size the problem before solving.\n2. **Define the convention.**\n   Write down: naming format, top-level folders, versioning rule. One page. Share with anyone who shares the files.\n3. **Create the structure.**\n   Top-level folders + `00 Inbox`. Don't over-build; start with 5-8 folders and grow as needed.\n4. **Process the backlog.**\n   Sort existing files in passes: delete obvious junk first, then file by project, rename key files. Timebox it — perfection isn't required.\n5. **Set up the inbox habit.**\n   All new files land in Inbox. Weekly 15-min processing: rename, file, or delete. The habit is the system.\n6. **Deduplicate.**\n   Run a duplicate finder quarterly. One canonical copy; aliases\u002Fshortcuts where a file is needed in two places.\n7. **Archive on completion.**\n   Finished projects move to Archive with a consistent structure. Active areas stay lean and truthful.\n8. **Maintain.**\n   Monthly: inbox zero, downloads cleared. Quarterly: archive sweep, duplicate check, convention review.\n\n## Common pitfalls\n\n- **Over-engineering folders.**\n  15 levels of taxonomy built before any files exist. Start flat; let structure emerge from real contents.\n- **'Final' versioning.**\n  final_v2_REAL_FINAL.docx. Explicit version numbers or git — the word 'final' is a lie.\n- **No inbox discipline.**\n  Files scattered across Desktop, Downloads, and Documents. One inbox, processed weekly, or chaos returns.\n- **Archiving nothing.**\n  Active folders clogged with 5-year-old projects. Archive on completion; active stays current.\n- **Inconsistent naming.**\n  Three date formats and random capitalization. The convention only works if everyone (including you) follows it always.\n- **Duplicate sprawl.**\n  Same file in email, downloads, desktop, and project folder. Canonical copy + links; dedupe quarterly.\n- **Organizing instead of deleting.**\n  Carefully filing files you'll never need. Delete first, organize second.\n- **No shared convention.**\n  Team members each inventing their own scheme in shared drives. Agree once, document, enforce kindly.\n","# File Organizer\n\n## Overview\n\nFile chaos has a cost: every search, every 'final_v2_REAL' confusion, every duplicated download burns time and trust.\n\nA working system: consistent naming, shallow meaningful folders, an inbox for unsorted files, and regular archiving.\n\nGoal: any file findable in 30 seconds via search or two folder clicks — months later, by future you.\n\n## When to use\n\n- Downloads folder with thousands of unsorted files\n- Setting up file organization on a new computer\n- 'final_v2_FINAL' version chaos in shared projects\n- Photo\u002Fdocument libraries growing unmanageable\n- Teams needing shared file conventions\n\n## Core concepts\n\n- **Naming conventions.**\n  `YYYY-MM-DD descriptive-name v03.ext`. Dates sort chronologically; descriptive names are searchable; versions are explicit. Agree once, use always.\n- **Shallow folders.**\n  2-3 levels deep max. Deep trees hide files; search + good names beat elaborate hierarchies.\n- **The inbox pattern.**\n  One `00 Inbox` folder for all new\u002Funsorted files. Process weekly: file, rename, or delete. Never browse the inbox as storage.\n- **PARA or project structure.**\n  Top level by actionability (Projects\u002FAreas\u002FResources\u002FArchive) or by project. Pick one; apply everywhere.\n- **Versioning discipline.**\n  Explicit versions (`v01`, `v02`) or version control (git) for documents. Never 'final', 'final2', 'final-FINAL'.\n- **Deduplication.**\n  Periodic sweeps for duplicates (same file, three locations). Hash-based tools find them reliably; keep one canonical copy.\n- **Archive vs. delete.**\n  Archive completed\u002Fold work (cheap storage); delete true junk (duplicates, installers, temp files). Archiving everything = hoarding.\n- **Search-first retrieval.**\n  Good names + OS search\u002Findexing. Train yourself to search rather than browse — it's faster once names are consistent.\n\n## Practical workflow\n\n1. **Audit the mess.**\n   Survey: where are files now, what's duplicated, what's the inbox situation. Size the problem before solving.\n2. **Define the convention.**\n   Write down: naming format, top-level folders, versioning rule. One page. Share with anyone who shares the files.\n3. **Create the structure.**\n   Top-level folders + `00 Inbox`. Don't over-build; start with 5-8 folders and grow as needed.\n4. **Process the backlog.**\n   Sort existing files in passes: delete obvious junk first, then file by project, rename key files. Timebox it — perfection isn't required.\n5. **Set up the inbox habit.**\n   All new files land in Inbox. Weekly 15-min processing: rename, file, or delete. The habit is the system.\n6. **Deduplicate.**\n   Run a duplicate finder quarterly. One canonical copy; aliases\u002Fshortcuts where a file is needed in two places.\n7. **Archive on completion.**\n   Finished projects move to Archive with a consistent structure. Active areas stay lean and truthful.\n8. **Maintain.**\n   Monthly: inbox zero, downloads cleared. Quarterly: archive sweep, duplicate check, convention review.\n\n## Common pitfalls\n\n- **Over-engineering folders.**\n  15 levels of taxonomy built before any files exist. Start flat; let structure emerge from real contents.\n- **'Final' versioning.**\n  final_v2_REAL_FINAL.docx. Explicit version numbers or git — the word 'final' is a lie.\n- **No inbox discipline.**\n  Files scattered across Desktop, Downloads, and Documents. One inbox, processed weekly, or chaos returns.\n- **Archiving nothing.**\n  Active folders clogged with 5-year-old projects. Archive on completion; active stays current.\n- **Inconsistent naming.**\n  Three date formats and random capitalization. The convention only works if everyone (including you) follows it always.\n- **Duplicate sprawl.**\n  Same file in email, downloads, desktop, and project folder. Canonical copy + links; dedupe quarterly.\n- **Organizing instead of deleting.**\n  Carefully filing files you'll never need. Delete first, organize second.\n- **No shared convention.**\n  Team members each inventing their own scheme in shared drives. Agree once, document, enforce kindly.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-file-organizer",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-file-organizer",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-file-organizer",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-file-organizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-file-organizer\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]