mcpbeat Sign in

File Organizer Agent Skill

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.

2k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill file-organizer

What comes with it

635 bytes besides the instruction
sub-skills/file-naming.md
sub-skills/folder-naming.md
sub-skills/when-to-archive.md

The instruction itself

9 sections, as written by the author

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 -rn

Summarize 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 -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
  • 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

🧠 Knowledge Modules (Fractal Skills)

1. Folder Naming

2. File Naming

3. When to Archive

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

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.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take dokhacgiakhoa/file-organizer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.