file-organizer
Skill1 starsChanged 8 months agoMITView on GitHub
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.
70 other projects use a version of this, 49 of them edited.
Adopted by
Most recently taken up by
- BrightGold70/skillsedited, first seen Nov 8, 2026
- insight68/Skillsedited, first seen Nov 8, 2026
- AlienHub/file-organizertheir own version, first seen Nov 8, 2026
- AgnesAI-Labs/agnet-skills-cntheir own version, first seen Nov 1, 2026
- digitaldevotion/ai-companion-alcoveedited, first seen Nov 1, 2026
- OpenSourceAssist/awesome-agent-skillsedited, first seen Nov 1, 2026
Used with
Projects with it also use skill-share, meeting-insights-analyzer and 9 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.
ArogyaReddySkillskill-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
ArogyaReddySkillmeeting-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
guaderramaSkilllead-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
trendinuxSkilltwitter-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
- +7 more from ArogyaReddy
Other versions70 projects use a version of this.
Word for word · 3
- xfstudio/skills★ 9100% same
- ai4brands-design/claude-skills★ 2100% same
- KellyDigitalArmy/ClaudeCode★ 0100% same
Edited · 49
- ComposioHQ/awesome-claude-skills★ 75k53% same
- ComposioHQ/awesome-codex-skills★ 17k53% same
- composio-community/awesome-codex-skills★ 16k53% same
- Prat011/awesome-llm-skills★ 1.7k53% same
- langchain-ai/deepagentsjs★ 1.6k55% same
- Prorise-cool/Claude-Code-Multi-Agent★ 30454% same
- ArogyaReddy/ComposioHQ-awesome-claude-skills★ 4553% same
- frostant/awesome-claude-skills★ 4453% same
- ammosu/awesome-claude-skills-zh-TW★ 2733% same
- Hassaan146/claude-skills★ 1853% same
39 more not listed
Wrote their own version · 18
- NVIDIA/SkillSpector★ 25ksame name
- smithjoshua/claude-code-cowork-skills-file-organizer★ 57same name
- Amazon-Quick/Amazon-Quick-official-catalog★ 50same name
- crazynomad/skills★ 27same name
- onlyoneaman/agent-skills★ 10same name
- AlienHub/file-organizer★ 7same name
- Cor-Incorporated/claude-code-skills★ 5same name
- megandmartin/agent-skills-repo★ 3same name
- zunyiqingfeng-code/skills★ 2same name
- AgnesAI-Labs/agnet-skills-cn★ 1same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- agent-reachSkill
- ai-image-generationSkill
- birdSkill
- code-simplifierSkill
- deep-researchSkill
- developer-growth-analysisSkill
- disk-cleanerSkill
- doubao-image-generationSkill
- e2e-testing-patternsSkill
- find-skillsSkill
- frontend-designSkill
- fullstack-developerSkill
- hr-skillSkill
- monitor-skillSkill
- multi-agent-workflowSkill
- obsidian-cliSkill
- pm-agentSkill
- podcast-skillSkill
- postbridge-social-growthSkill
- proactive-agentSkill
- tavilySkill
- tinybirdSkill
- twitter-readerSkill
- webapp-testingSkill
- xhs-note-creatorSkill
The file
We split this skill into the rules it gives an agent
11 rules. 11 are common, 0 are distinctive, and 0 are very specific to this project.
11
Common
Most of the 60 edited versions we read keep these.
0
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
- Common: line 29
When a user requests file organization help:
- Common: line 96
When requested, search for duplicates:
- Common: line 114
Important: Always ask for confirmation before deleting
- Common: line 164
After approval, organize systematically:
- Common: line 179
Always confirm before deleting anything
- Common: line 183
Stop and ask if you encounter unexpected situations
- Common: line 233
Use clear, descriptive names
- Common: line 234
Avoid spaces (use hyphens or underscores)
- Common: line 236
Use prefixes for ordering: "01-current", "02-archive"
- Common: line 242
Avoid version numbers in names (use version control instead)
- Common: line 243
Remove download artifacts: "document-final-v2 (1).pdf" → "document.pdf"
“Common” is measured: kept by at least 6 in 10 of the 60 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.
Files
File Organizer
When to Use This Skill
- Your Downloads folder is a chaotic mess
- You can't find files because they're scattered everywhere
- You have duplicate files taking up space
- Your folder structure doesn't make sense anymore
- You want to establish better organization habits
- You're starting a new project and need a good structure
- You're cleaning up before archiving old projects
What This Skill Does
- Analyzes Current Structure: Reviews your folders and files to understand what you have
- Finds Duplicates: Identifies duplicate files across your system
- Suggests Organization: Proposes logical folder structures based on your content
- Automates Cleanup: Moves, renames, and organizes files with your approval
- Maintains Context: Makes smart decisions based on file types, dates, and content
- Reduces Clutter: Identifies old files you probably don't need anymore
Instructions
When a user requests file organization help:
Understand the Scope
Ask clarifying questions:
- Which directory needs organization? (Downloads, Documents, entire home folder?)
- What's the main problem? (Can't find things, duplicates, too messy, no structure?)
- Any files or folders to avoid? (Current projects, sensitive data?)
- How aggressively to organize? (Conservative vs. comprehensive cleanup)
Analyze Current State
Review the target directory:
# Get overview of current structure ls -la [target_directory] # Check file types and sizes find [target_directory] -type f -exec file {} \; | head -20 # Identify largest files du -sh [target_directory]/* | sort -rh | head -20 # Count file types find [target_directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rnSummarize findings:
- Total files and folders
- File type breakdown
- Size distribution
- Date ranges
- Obvious organization issues
Identify Organization Patterns
Based on the files, determine logical groupings:
By Type:
- Documents (PDFs, DOCX, TXT)
- Images (JPG, PNG, SVG)
- Videos (MP4, MOV)
- Archives (ZIP, TAR, DMG)
- Code/Projects (directories with code)
- Spreadsheets (XLSX, CSV)
- Presentations (PPTX, KEY)
By Purpose:
- Work vs. Personal
- Active vs. Archive
- Project-specific
- Reference materials
- Temporary/scratch files
By Date:
- Current year/month
- Previous years
- Very old (archive candidates)
Find Duplicates
When requested, search for duplicates:
# Find exact duplicates by hash find [directory] -type f -exec md5 {} \; | sort | uniq -d # Find files with similar names find [directory] -type f -printf '%f\n' | sort | uniq -d # Find similar-sized files find [directory] -type f -printf '%s %p\n' | sort -nFor each set of duplicates:
- Show all file paths
- Display sizes and modification dates
- Recommend which to keep (usually newest or best-named)
- Important: Always ask for confirmation before deleting
Propose Organization Plan
Present a clear plan before making changes:
# Organization Plan for [Directory] ## Current State - X files across Y folders - [Size] total - File types: [breakdown] - Issues: [list problems] ## Proposed Structure [Directory]/ ├── Work/ │ ├── Projects/ │ ├── Documents/ │ └── Archive/ ├── Personal/ │ ├── Photos/ │ ├── Documents/ │ └── Media/ └── Downloads/ ├── To-Sort/ └── Archive/ ## Changes I'll Make 1. **Create new folders**: [list] 2. **Move files**: - X PDFs → Work/Documents/ - Y images → Personal/Photos/ - Z old files → Archive/ 3. **Rename files**: [any renaming patterns] 4. **Delete**: [duplicates or trash files] ## Files Needing Your Decision - [List any files you're unsure about] Ready to proceed? (yes/no/modify)Execute Organization
After approval, organize systematically:
# Create folder structure mkdir -p "path/to/new/folders" # Move files with clear logging mv "old/path/file.pdf" "new/path/file.pdf" # Rename files with consistent patterns # Example: "YYYY-MM-DD - Description.ext"Important Rules:
- Always confirm before deleting anything
- Log all moves for potential undo
- Preserve original modification dates
- Handle filename conflicts gracefully
- Stop and ask if you encounter unexpected situations
Provide Summary and Maintenance Tips
After organizing:
# Organization Complete! ✨ ## What Changed - Created [X] new folders - Organized [Y] files - Freed [Z] GB by removing duplicates - Archived [W] old files ## New Structure [Show the new folder tree] ## Maintenance Tips To keep this organized: 1. **Weekly**: Sort new downloads 2. **Monthly**: Review and archive completed projects 3. **Quarterly**: Check for new duplicates 4. **Yearly**: Archive old files ## Quick Commands for You # Find files modified this week find . -type f -mtime -7 # Sort downloads by type [custom command for their setup] # Find duplicates [custom command]Want to organize another folder?
Best Practices
Folder Naming
- Use clear, descriptive names
- Avoid spaces (use hyphens or underscores)
- Be specific: "client-proposals" not "docs"
- Use prefixes for ordering: "01-current", "02-archive"
File Naming
- Include dates: "2024-10-17-meeting-notes.md"
- Be descriptive: "q3-financial-report.xlsx"
- Avoid version numbers in names (use version control instead)
- Remove download artifacts: "document-final-v2 (1).pdf" → "document.pdf"
When to Archive
- Projects not touched in 6+ months
- Completed work that might be referenced later
- Old versions after migration to new systems
- Files you're hesitant to delete (archive first)
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
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.

