F

file-organizer

Verified

by ComposioHQ · Updated Apr 16, 2026

opus
341in15.2Kout
$1.175m 45s

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.

file-managementorganizationdeduplicationcleanupfolderslocal-files

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. my Downloads is a disaster and IT needs it cleaned up before today's compliance check — organize it conservatively, skip any repo folders, and give me a cleanup summary

Let me start by analyzing your Downloads folder.

The ~ is pointing to a sandboxed temp directory. Let me find your real Downloads folder.

8.2 GB across 199 files and many folders. Let me get the full picture.

Good -- no git repos found. I can see 199 files (8.2 GB) plus ~90 subdirectories. Here's what I'm seeing:

  • 16 safetensors (ML model weights, ~4+ GB)
  • 11 DMGs (installers, ~1.7 GB) including a duplicate Claude.dmg
  • 28 images (jpg/png/webp), 14 videos (mp4), 4 gifs
  • 26 CSVs, 21 ZIPs, various docs
  • ~30 UUID-named folders and ~40 AI training output folders
  • 2 incomplete downloads (.crdownload)
  • Sensitive files: client_secret_*.json, stripe_backup_code.txt

Let me organize this now -- nothing gets deleted, just sorted into clear folders.

Now let me move files in batches. I'll handle duplicates by moving the (1), (2), etc. copies to _Duplicates.

Now let me move all the AI training output folders and UUID folders.

Now let me verify what's left and generate the summary.

All files moved. The only thing left is the existing Archive folder which I intentionally preserved. Let me get final stats.

Done. Here's your cleanup summary:


Downloads Cleanup Summary

Before

199 loose files + ~90 folders scattered across ~/Downloads (8.2 GB)

After -- New Structure

~/Downloads/
  _Organized/
    Installers/       13 items   (1.7 GB)  -- DMGs, app bundles
    ML-Models/        15 files   (4.5 GB)  -- .safetensors weights
    Images/           72 files   (118 MB)  -- png/jpg/webp/gif
    Videos/           10 files   (23 MB)   -- mp4
    Data/             22 files   (8.8 MB)  -- csv/json/xlsm/numbers
    Documents/        17 items   (29 MB)   -- pdf/epub/html/md/txt
    Archives/         20 items   (201 MB)  -- zip/tar.gz + extracted dirs
    AI-Training-Outputs/ 63 folders (936 MB) -- flux/wan/qwen/sdxl/ltx2/etc.
    UUID-Outputs/     33 folders  (85 MB)  -- UUID-named generation outputs
    Config/            5 files   (99 MB)   -- .conf/.diff + incomplete downloads
  _Duplicates/        29 files   (537 MB)  -- safe to delete after review
  _Flagged-Sensitive/  3 files             -- needs your attention
  Archive/            (existing, untouched)

Duplicates Identified (537 MB recoverable)

  • Claude (1).dmg -- exact copy of Claude.dmg (248 MB)
  • qi_yaelaris_s700_l2_b4 (1).safetensors (281 MB)
  • 5x skill_detail_analytics CSV copies
  • 3x anthropics-...-frontend-design-skill-md ZIPs
  • 2x affaan-m-...-market-research-skill-md ZIPs
  • 2x unified_payments CSVs, 2x validation.md, 2x index.html, and more

Compliance Flags

  • _Flagged-Sensitive/client_secret_*.json -- Google OAuth client secret. Move to a secure vault or delete.
  • _Flagged-Sensitive/stripe_backup_code.txt -- Stripe backup codes. Should not be in Downloads.
  • _Flagged-Sensitive/insoul-*.json -- Firebase/service credentials. Review and secure.
  • 2 incomplete downloads (.crdownload) in Config -- can be deleted.

What Was Preserved

  • Existing Archive/ folder (untouched)
  • .accelerate/ config (untouched)
  • No files were deleted -- everything was moved, nothing lost
  • No git repos found (none to skip)

Next steps: Review _Duplicates/ and delete what you don't need (frees ~537 MB). Move or delete the 3 files in _Flagged-Sensitive/ before the compliance check.

Claude Sonnet 4.6

Permissions

ScopeDescription
filesystem:read
filesystem:write
filesystem:delete

SKILL.md

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

  1. Analyzes Current Structure: Reviews your folders and files to understand what you have
  2. Finds Duplicates: Identifies duplicate files across your system
  3. Suggests Organization: Proposes logical folder structures based on your content
  4. Automates Cleanup: Moves, renames, and organizes files with your approval
  5. Maintains Context: Makes smart decisions based on file types, dates, and content
  6. 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 folder
Find duplicate files in my Documents folder
Review my project directories and suggest improvements

Specific Organization Tasks

Organize these downloads into proper folders based on what they are
Find duplicate files and help me decide which to keep
Clean up old files I haven't touched in 6+ months
Create a better folder structure for my [work/projects/photos/etc]

Instructions

When a user requests file organization help:

  1. 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)
  2. 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 -rn
    

    Summarize findings:

    • Total files and folders
    • File type breakdown
    • Size distribution
    • Date ranges
    • Obvious organization issues
  3. 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)
  4. 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 -n
    

    For 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
  5. 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)
    
  6. 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
  7. 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:

  1. Analyzes Downloads folder
  2. Finds patterns: work docs, personal photos, installers, random PDFs
  3. Proposes structure:
    • Downloads/
      • Work/
      • Personal/
      • Installers/ (DMG, PKG files)
      • Archive/
      • ToSort/ (things needing decisions)
  4. Asks for confirmation
  5. Moves files intelligently based on content and names
  6. 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

  1. Start Small: Begin with one messy folder (like Downloads) to build trust
  2. Regular Maintenance: Run weekly cleanup on Downloads
  3. Consistent Naming: Use "YYYY-MM-DD - Description" format for important files
  4. Archive Aggressively: Move old projects to Archive instead of deleting
  5. Keep Active Separate: Maintain clear boundaries between active and archived work
  6. 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

FAQ

What does file-organizer do?

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.

When should I use file-organizer?

Use it when you need a repeatable workflow that produces text response.

What does file-organizer output?

In the evaluated run it produced text response.

How do I install or invoke file-organizer?

npx skills add https://github.com/composiohq/awesome-claude-skills --skill file-organizer

Which agents does file-organizer support?

Claude Code

What tools, channels, or permissions does file-organizer need?

It uses no extra tools; channels commonly include text; permissions include filesystem:read, filesystem:write, filesystem:delete.

Is file-organizer safe to install?

Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.

How is file-organizer different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does file-organizer outperform not using a skill?

About file-organizer

When to use file-organizer

A Downloads, Documents, Desktop, or Projects folder has become cluttered and hard to navigate. You want help finding duplicate files and deciding what to keep. You want to restructure local folders into a clearer archive, active, or category-based layout.

When file-organizer is not the right choice

You need to organize files in remote cloud services or external SaaS platforms. You want a read-only audit with no possibility of file moves, renames, or deletions.

What it produces

Produces text response.

Install

npx skills add https://github.com/composiohq/awesome-claude-skills --skill file-organizer

Invoke: Ask Claude Code to use file-organizer for the task.