agentleFS
AgnesAI-LabsAgnesAI-Labs/agnet-skills-cn/file-organizer/SKILL.md

file-organizer

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Organize and rename files based on content analysis

70 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use skill-share, meeting-insights-analyzer and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArogyaReddySkill

    skill-share

    A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

    Also in 25 projects that use this

  • ArogyaReddySkill

    meeting-insights-analyzer

    Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.

    Also in 39 projects that use this

  • guaderramaSkill

    lead-research-assistant

    Identifies and qualifies potential leads by analyzing products/services, understanding ideal customer profiles, conducting intelligent web research using Bright Data MCP tools, and providing actionable outreach strategies. Use when researching leads, prospecting, qualifying contacts, analyzing companies, enriching lead data, or creating outreach campaigns.

    Also in 36 projects that use this

  • trendinuxSkill

    twitter-algorithm-optimizer

    Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.

    Also in 14 projects that use this

  • +8 more from ArogyaReddy

The file

We split this skill into the rules it gives an agent

7 rules. 1 is common, 6 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 63 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use underscores or hyphens, not spaces

    line 81
  2. Distinctive:

    Start with date for chronological sorting

    line 82
  3. Distinctive:

    Add version numbers for iterations

    line 84
  4. Distinctive:

    Keep names concise but descriptive

    line 85
  5. Distinctive:

    Flat is Better: Avoid deep nesting (max 3-4 levels)

    line 237
  6. Distinctive:

    Delete duplicates and temp files

    line 241
  7. Distinctive:

    Use cloud sync for important files

    line 243

“Common” is measured: kept by at least 6 in 10 of the 63 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

## 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 folder

Best 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.