file-organizer
Skill4 starsChanged 26 days agoMITView on GitHub
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
71 other projects use a version of this, 22 of them edited; 0 new projects in the last 4 weeks, against 1 the 4 before.
Adopted by
Cooling: 0 new projects took it in the last 4 weeks, 0× the 4 weeks before.thin data
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-skillsword for word, first seen Nov 1, 2026
Used with
Projects with it also use lead-research-assistant, connect-apps and 3 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.
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
ArogyaReddySkillconnect-apps
Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.
Also in 18 projects that use this
ArogyaReddySkilltailored-resume-generator
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Also in 28 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
- +1 more from ArogyaReddy
Other versions71 projects use a version of this.
Word for word · 32
- ComposioHQ/awesome-claude-skills★ 75k100% same
- ComposioHQ/awesome-codex-skills★ 17k100% same
- composio-community/awesome-codex-skills★ 16k100% same
- Prat011/awesome-llm-skills★ 1.7k100% same
- ArogyaReddy/ComposioHQ-awesome-claude-skills★ 45100% same
- frostant/awesome-claude-skills★ 44100% same
- Hassaan146/claude-skills★ 18100% same
- OpenSourceAssist/awesome-agent-skills★ 17100% same
- Engineer1999/A-Curated-List-of-Awesome-Claude-Skills★ 4100% same
- GPTtang/skill-atlas★ 4100% same
22 more not listed
Edited · 22
- langchain-ai/deepagentsjs★ 1.6k87% same
- Prorise-cool/Claude-Code-Multi-Agent★ 30499% same
- ammosu/awesome-claude-skills-zh-TW★ 2781% same
- xfstudio/skills★ 994% same
- insight68/Skills★ 599% same
- whz39coding/zh-awesome-codex-skills★ 499% same
- Crumbgrabber/llm_system_template_agents_skills_patterns_tools_prompts★ 399% same
- ai4brands-design/claude-skills★ 294% same
- digitaldevotion/ai-companion-alcove★ 272% same
- julweber/ai_agent_skills★ 2100% same
12 more not listed
Wrote their own version · 17
- 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
7 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 repository169 other files it gives its agents.
- epub-skill/CLAUDE.mdCLAUDE.md
- linear-cli-skill/CLAUDE.mdCLAUDE.md
- AgentDB Advanced FeaturesSkill
- AgentDB Learning PluginsSkill
- AgentDB Memory PatternsSkill
- AgentDB Performance OptimizationSkill
- AgentDB Vector SearchSkill
- agent-evalSkill
- agentic-jujutsuSkill
- agile-product-ownerSkill
- ai-tool-pickerSkill
- algorithmic-artSkill
- api-connectorSkill
- api-design-patternsSkill
- architecture-diagram-creatorSkill
- article-extractorSkill
- aws-agentic-aiSkill
- aws-cdk-developmentSkill
- aws-cost-operationsSkill
- aws-serverless-edaSkill
- biogeobearsSkill
- brainstormingSkill
- brand-guidelinesSkill
- canvas-designSkill
- capa-officerSkill
- ceo-advisorSkill
- changelog-generatorSkill
- code-auditorSkill
- codebase-documenterSkill
- code-executionSkill
- code-explainerSkill
- code-refactorSkill
- code-reviewerSkill
- code-transferSkill
- content-creatorSkill
- content-research-writerSkill
- conversation-analyzerSkill
- csv-data-summarizerSkill
- cto-advisorSkill
- d3-vizSkill
- dashboard-creatorSkill
- defense-in-depthSkill
- deploy-itSkill
- developer-growth-analysisSkill
- dispatching-parallel-agentsSkill
- doc-coauthoringSkill
- docxSkill
- domain-name-brainstormerSkill
- dwa-councilSkill
- error-fixerSkill
- escalation-reasoningSkill
- evaluator-optimizerSkill
- executing-plansSkill
- extract-from-pdfsSkill
- fda-consultant-specialistSkill
- feature-planningSkill
- file-operationsSkill
- finishing-a-development-branchSkill
- firebase-buddySkill
- flowchart-creatorSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 1 is common, 12 are distinctive, and 0 are very specific to this project.
1
Common
Most of the 32 edited versions we read keep these.
12
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
- Distinctive: line 71
When a user requests file organization help:
- Distinctive: line 132
When requested, search for duplicates:
- Distinctive: line 148
Important: Always ask for confirmation before deleting
- Distinctive: line 199
After approval, organize systematically:
- Distinctive: line 213
Always confirm before deleting anything
- Distinctive: line 217
Stop and ask if you encounter unexpected situations
- Distinctive: line 400
Regular Maintenance: Run weekly cleanup on Downloads
- Distinctive: line 401
Consistent Naming: Use "YYYY-MM-DD - Description" format for important files
- Distinctive: line 409
Use clear, descriptive names
- Common: line 410
Avoid spaces (use hyphens or underscores)
- Distinctive: line 412
Use prefixes for ordering: "01-current", "02-archive"
- Distinctive: line 417
Avoid version numbers in names (use version control instead)
- Distinctive: line 418
Remove download artifacts: "document-final-v2 (1).pdf" → "document.pdf"
“Common” is measured: kept by at least 6 in 10 of the 32 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
This skill acts as your personal organization assistant, helping you maintain a clean, logical file structure across your computer without the mental overhead of constant manual organization.
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
How to Use
From Your Home Directory
cd ~Then run Claude Code and ask for help:
Help me organize my Downloads folderFind duplicate files in my Documents folderReview my project directories and suggest improvementsSpecific Organization Tasks
Organize these downloads into proper folders based on what they areFind duplicate files and help me decide which to keepClean up old files I haven't touched in 6+ monthsCreate a better folder structure for my [work/projects/photos/etc]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 same name 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 ```bash # 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?
Examples
Example 1: Organizing Downloads (From Justin Dielmann)
User: "My Downloads folder is a mess with 500+ files. Help me organize it."
Process:
- Analyzes Downloads folder
- Finds patterns: work docs, personal photos, installers, random PDFs
- Proposes structure:
- Downloads/
- Work/
- Personal/
- Installers/ (DMG, PKG files)
- Archive/
- ToSort/ (things needing decisions)
- Downloads/
- Asks for confirmation
- Moves files intelligently based on content and names
- Results: 500 files → 5 organized folders
Example 2: Finding and Removing Duplicates
User: "Find duplicate files in my Documents and help me decide which to keep."
Output:
# Found 23 Sets of Duplicates (156 MB total)
## Duplicate Set 1: "proposal.pdf"
- `/Documents/proposal.pdf` (2.3 MB, modified: 2024-03-15)
- `/Documents/old/proposal.pdf` (2.3 MB, modified: 2024-03-15)
- `/Desktop/proposal.pdf` (2.3 MB, modified: 2024-03-10)
**Recommendation**: Keep `/Documents/proposal.pdf` (most recent in correct location)
Delete the other 2 copies?
[Continue for all duplicates...]Example 3: Restructuring Projects Folder
User: "Review my ~/Projects directory and suggest improvements."
Output:
# Analysis of ~/Projects
## Current Structure Issues
- Mix of active and archived projects (3+ years old)
- No consistent naming convention
- Some projects at root, others in random subfolders
- Duplicate folders (project-name, project-name-old, project-name-v2)
## Proposed Structure
Projects/ ├── Active/ │ ├── client-work/ │ ├── side-projects/ │ └── learning/ ├── Archive/ │ ├── 2022/ │ ├── 2023/ │ └── 2024/ └── Templates/
## Specific Changes
1. Move 12 projects not touched since 2022 → Archive/
2. Consolidate 4 duplicate project folders
3. Rename projects to consistent format: "client-name-project-name"
4. Create Archive for old work
Want me to implement this?Example 4: Organizing Photos by Date
User: "Organize my photo folders by year and month."
Output: Creates structure like:
Photos/
├── 2023/
│ ├── 01-January/
│ ├── 02-February/
│ └── ...
├── 2024/
│ ├── 01-January/
│ └── ...
└── Unsorted/Then moves photos based on EXIF data or file modification dates.
Common Organization Tasks
Downloads Cleanup
Organize my Downloads folder - move documents to Documents,
images to Pictures, keep installers separate, and archive files
older than 3 months.Project Organization
Review my Projects folder structure and help me separate active
projects from old ones I should archive.Duplicate Removal
Find all duplicate files in my Documents folder and help me
decide which ones to keep.Desktop Cleanup
My Desktop is covered in files. Help me organize everything into
my Documents folder properly.Photo Organization
Organize all photos in this folder by date (year/month) based
on when they were taken.Work/Personal Separation
Help me separate my work files from personal files across my
Documents folder.Pro Tips
- Start Small: Begin with one messy folder (like Downloads) to build trust
- Regular Maintenance: Run weekly cleanup on Downloads
- Consistent Naming: Use "YYYY-MM-DD - Description" format for important files
- Archive Aggressively: Move old projects to Archive instead of deleting
- Keep Active Separate: Maintain clear boundaries between active and archived work
- Trust the Process: Let Claude handle the cognitive load of where things go
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)
Related Use Cases
- Setting up organization for a new computer
- Preparing files for backup/archiving
- Cleaning up before storage cleanup
- Organizing shared team folders
- Structuring new project directories
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.

