
File Organizer
- 4.5k installs
- 357 repo stars
- Updated January 31, 2026
- claude-office-skills/skills
A skill that reads file contents and metadata to propose categorization, naming conventions, folder hierarchies, duplicate reports, and automation rules without executing file moves directly.
About
File Organizer is a skill that analyzes file contents and metadata to generate categorization suggestions, naming conventions, folder structures, and duplicate reports. Developers and teams use it when managing unstructured downloads, project assets, client deliverables, or archival workflows. Key workflows include content-based categorization across documents, financial files, media, code, and data; applying date-first naming formats such as YYYY-MM-DD_Category_Description_v1.ext; producing file mapping tables with original name, new name, and destination; and generating automation rules that trigger on file type or content patterns. It integrates with the office-mcp server via the analyze_document_structure tool. Recommended models are claude-sonnet-4 and claude-opus-4, with gpt-4 and gpt-4o listed as compatible. Manual review is recommended for important files, and protected or encrypted files are out of scope. Generates naming conventions for documents, images, invoices, and meeting notes using date-first YYYY-MM-DD patterns
- Generates naming conventions for documents, images, invoices, and meeting notes using date-first YYYY-MM-DD patterns
- Produces folder tree structures for personal documents, project-based layouts, and client/vendor hierarchies up to 4 lev
- Outputs a file mapping table showing original name, proposed new name, and destination folder for each file
- Detects exact duplicates and similar files, reporting recoverable space and recommended keep locations
- Supports automation rules triggered by file content patterns such as PDF invoices or Screenshots matching a glob
File Organizer by the numbers
- 4,464 all-time installs (skills.sh)
- +80 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #123 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
file organizer capabilities & compatibility
- Capabilities
- file_categorization · naming_convention · organization · duplicate_detection · metadata_extraction · automation_rules · folder_structure_generation
- Use cases
- documentation · project management · planning
- Runs
- Runs locally
- Pricing
- Free
What file organizer says it does
YYYY-MM-DD_Category_Description_v1.ext Example: 2026-01-29_Contract_ClientName_NDA_v1.pdf
mcp: server: office-mcp tools: - analyze_document_structure
npx skills add https://github.com/claude-office-skills/skills --skill file-organizerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4.5k |
|---|---|
| repo stars | ★ 357 |
| Security audit | 3 / 3 scanners passed |
| Last updated | January 31, 2026 |
| Repository | claude-office-skills/skills ↗ |
What it does
Analyze file contents and metadata to suggest folder structures, consistent naming conventions, duplicate detection, and automation rules for organizing project or personal files.
Who is it for?
Teams or individual developers managing large collections of project assets, client deliverables, invoices, or media files that need consistent naming and structure.
Skip if: Scenarios requiring direct encrypted or protected file access, or automated bulk file moves without human review.
When should I use this skill?
A developer needs to clean up a downloads folder, standardize invoice naming, organize project deliverables, or set up recurring file hygiene rules.
What you get
Produces an actionable organization plan including a folder tree, file mapping table, duplicate report, and automation rules that a developer can review and execute.
- File organization plan with folder tree and file mapping table
- Duplicate files report showing recoverable space and keep recommendations
- Automation rules document for ongoing file hygiene
By the numbers
- 5 content-based categories supported: Documents, Financial, Media, Code, Data
- 3 pre-built folder structure templates: Personal Documents, Project-Based, Client/Vendor
- 3 example automation rules documented for invoices, screenshots, and downloads cleanup
Files
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.pdfImages
YYYY-MM-DD_Event/Project_Description_NNN.ext
Example: 2026-01-29_ProductLaunch_HeroImage_001.pngInvoices/Receipts
YYYY-MM-DD_Vendor_Amount_InvoiceNumber.ext
Example: 2026-01-29_Adobe_149.99_INV-12345.pdfMeeting Notes
YYYY-MM-DD_MeetingType_Topic.ext
Example: 2026-01-29_TeamSync_Q1Planning.mdNaming 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
└── 📁 ArchiveClient/Vendor
📁 Clients
└── 📁 [ClientName]
├── 📁 Contracts
├── 📁 Projects
│ └── 📁 [ProjectName]
├── 📁 Invoices
├── 📁 Communications
└── 📁 AssetsOutput Formats
Organization Plan
## 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
## Duplicate Files Report
**Total Duplicates Found**: [Count]
**Space Recoverable**: [Size]
### Exact Duplicates
| File | Locations | Size | Recommendation |
|------|-----------|------|----------------|
| report.pdf | /Downloads/, /Documents/ | 2.3MB | Keep in /Documents/ |
### Similar Files
| Files | Similarity | Difference |
|-------|------------|------------|
| report_v1.pdf, report_v2.pdf | 95% | v2 has extra page |Analysis Capabilities
Content-Based Categorization
- Documents: Contracts, reports, letters, forms
- Financial: Invoices, receipts, statements, budgets
- Media: Photos, videos, audio, graphics
- Code: Source files, configs, documentation
- Data: Spreadsheets, databases, exports
Metadata Extraction
- Creation/modification dates
- Author information
- File dimensions (images/video)
- Duration (audio/video)
- Page count (documents)
Automation Rules
Example Rules
## Auto-Organization Rules
### Rule 1: Invoices
- Trigger: PDF with "Invoice" or "INV-" in content
- Action: Move to /Finance/Invoices/[Year]/[Month]/
- Rename: YYYY-MM-DD_Vendor_Amount.pdf
### Rule 2: Screenshots
- Trigger: File matches "Screenshot*.png"
- Action: Move to /Screenshots/[Year-Month]/
- Rename: YYYY-MM-DD_HH-MM_Screenshot.png
### Rule 3: Downloads Cleanup
- Trigger: File in Downloads older than 30 days
- Action:
- If document → Archive
- If installer → Delete
- If media → Sort to appropriate folderBest Practices
Organization Principles
1. PARA Method: Projects, Areas, Resources, Archive 2. Date-First: Enables chronological sorting 3. Descriptive Names: Future you will thank you 4. Flat is Better: Avoid deep nesting (max 3-4 levels) 5. Regular Maintenance: Schedule monthly reviews
File Hygiene
- Delete duplicates and temp files
- Archive completed projects
- Use cloud sync for important files
- Maintain consistent naming
- Document your system
Limitations
- Cannot access protected/encrypted files
- Large file moves require manual execution
- Content analysis depends on file format support
- Cannot guarantee perfect categorization
- Manual review recommended for important files
Related skills
How it compares
Use file-organizer for content-based directory cleanup, not for IDE refactoring or git history-preserving code moves.
FAQ
What naming format does the skill recommend for documents?
YYYY-MM-DD_Category_Description_v1.ext, for example 2026-01-29_Contract_ClientName_NDA_v1.pdf, with underscores instead of spaces and a version suffix.
Can the skill move files automatically?
No. The skill produces an organization plan and file mapping table for review; large file moves require manual execution per the documented limitations.
Which AI models are compatible with this skill?
Recommended models are claude-sonnet-4 and claude-opus-4; compatible models include claude-3-5-sonnet, gpt-4, and gpt-4o.
Is File Organizer safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.