File Organizer
Turn messy downloads and project folders into consistent names, categories, and folder structures from content analysis.
Overview
File Organizer is a journey-wide agent skill that organizes and renames files from content analysis—usable whenever a solo builder needs to clear folder chaos before committing to the next task.
Install
npx skills add https://github.com/claude-office-skills/skills --skill file-organizerWhat is this skill?
- Analyzes document structure and content to suggest categories and filenames
- Proposes folder hierarchies and naming conventions for projects or downloads
- Identifies duplicate files and consolidation options
- Integrates with office-mcp analyze_document_structure for deeper reads
- Supports English and Chinese prompt workflows
Adoption & trust: 2.9k installs on skills.sh; 196 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your project, download, or shared drive folders are inconsistent and hard to search, so you waste time finding the right asset.
Who is it for?
Indie builders juggling specs, exports, contracts, and assets across Idea through Operate without a dedicated ops assistant.
Skip if: Teams that already enforce rigid DAM or git-only artifact policies where automated rename suggestions would conflict with tooling.
When should I use this skill?
You want files analyzed for category, naming, folder structure, or duplicate handling.
What do I get? / Deliverables
You receive a proposed folder structure, naming scheme, categorization rationale, and duplicate handling steps you can execute in one cleanup pass.
- Proposed folder tree
- Naming convention rules
- Duplicate and categorization recommendations
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Sort competitor PDFs and interview notes into labeled research folders.
Rename screenshot and screen recording exports from a prototype sprint.
Standardize spec, API, and design filenames before handing work to an agent.
Organize launch copy, creatives, and press assets under one convention.
Reset a cluttered downloads directory after a support ticket attachment binge.
How it compares
Use for semantic file triage and naming plans—not for bulk cloud sync, enterprise ECM, or code repository refactors.
Common Questions / FAQ
Who is file organizer for?
Solo builders and small teams who want AI-assisted categorization and renaming for local or office document piles.
When should I use file organizer?
During Idea when sorting research dumps; in Validate when filing prototype captures; in Build for spec and asset folders; before Launch for marketing assets; in Operate when downloads or client files need a reset.
Is file organizer safe to install?
Review the Security Audits panel on this page; the skill may read file contents via MCP—avoid pointing it at secrets-heavy directories without redaction.
SKILL.md
READMESKILL.md - File Organizer
# File Organizer Intelligently organize and rename files based on their content and metadata. ## Overview This skill helps you: - Analyze file contents to determine categorization - Suggest folder structures - Generate consistent naming conventions - Identify and handle duplicates - Create organization systems ## How to Use ### Analyze Files ``` "Analyze these files and suggest how to organize them" "What category does this file belong to?" "Suggest a better filename for this document" ``` ### Organize ``` "Create a folder structure for my project files" "Organize my downloads folder" "Sort these invoices by vendor and date" ``` ## Naming Conventions ### Recommended Formats **Documents** ``` YYYY-MM-DD_Category_Description_v1.ext Example: 2026-01-29_Contract_ClientName_NDA_v1.pdf ``` **Images** ``` YYYY-MM-DD_Event/Project_Description_NNN.ext Example: 2026-01-29_ProductLaunch_HeroImage_001.png ``` **Invoices/Receipts** ``` YYYY-MM-DD_Vendor_Amount_InvoiceNumber.ext Example: 2026-01-29_Adobe_149.99_INV-12345.pdf ``` **Meeting Notes** ``` YYYY-MM-DD_MeetingType_Topic.ext Example: 2026-01-29_TeamSync_Q1Planning.md ``` ### Naming Rules - Use underscores or hyphens, not spaces - Start with date for chronological sorting - Include key identifiers (client, project, type) - Add version numbers for iterations - Keep names concise but descriptive ## Folder Structures ### Personal Documents ``` 📁 Documents ├── 📁 Admin │ ├── 📁 Finance │ │ ├── 📁 Invoices │ │ ├── 📁 Receipts │ │ └── 📁 Tax │ ├── 📁 Insurance │ └── 📁 Legal ├── 📁 Work │ ├── 📁 Projects │ ├── 📁 Reports │ └── 📁 Meetings ├── 📁 Personal │ ├── 📁 Health │ ├── 📁 Education │ └── 📁 Travel └── 📁 Archive └── 📁 [Year] ``` ### Project-Based ``` 📁 ProjectName ├── 📁 01_Planning │ ├── 📁 Requirements │ ├── 📁 Proposals │ └── 📁 Research ├── 📁 02_Design │ ├── 📁 Mockups │ ├── 📁 Assets │ └── 📁 Specs ├── 📁 03_Development │ ├── 📁 Source │ ├── 📁 Tests │ └── 📁 Documentation ├── 📁 04_Deliverables │ └── 📁 [Version] ├── 📁 05_Admin │ ├── 📁 Contracts │ ├── 📁 Invoices │ └── 📁 Communications └── 📁 Archive ``` ### Client/Vendor ``` 📁 Clients └── 📁 [ClientName] ├── 📁 Contracts ├── 📁 Projects │ └── 📁 [ProjectName] ├── 📁 Invoices ├── 📁 Communications └── 📁 Assets ``` ## Output Formats ### Organization Plan ```markdown ## File Organization Plan **Source**: [Folder/Location] **Total Files**: [Count] **Total Size**: [Size] ### Proposed Structure [Folder tree] ### File Mapping | Original Name | New Name | Destination | |--------------|----------|-------------| | IMG_1234.jpg | 2026-01-29_ProductPhoto_001.jpg | /Products/Photos/ | | doc1.pdf | 2026-01-15_Contract_ClientA_NDA.pdf | /Clients/ClientA/Contracts/ | ### Actions Required 1. Create folders: [list] 2. Rename files: [count] 3. Move files: [count] 4. Review manually: [count with reasons] ``` ### Duplicate Report ```markdown ## Duplicate Files Report **Total Duplicates Found**: [Count] **Space Recoverable**: [Size] ### Exact Duplicates |