
File Organizer
- 1k installs
- 44k repo stars
- Updated July 27, 2026
- sickn33/antigravity-awesome-skills
file-organizer is a filesystem productivity skill that analyzes, deduplicates, renames, and intelligently reorganizes project files and folders with full user approval gates before any changes apply.
About
file-organizer is a community skill from sickn33/antigravity-awesome-skills for cleaning chaotic directories on a developer machine. It analyzes the current folder structure, finds duplicate files, proposes renames, identifies old low-value files, and suggests a clearer hierarchy—all behind approval gates so nothing moves without consent. Developers reach for file-organizer when Downloads is unusable, project assets are scattered, duplicates waste disk space, or a new repo needs a sane layout before archiving old work. The skill covers six documented capabilities including clutter reduction for stale files. It fits pre-archive cleanup and establishing organization habits rather than runtime application debugging.
- Analyzes current folder structures and file metadata
- Detects and surfaces duplicate files across directories
- Proposes logical organization schemes based on content, type, and date
- Automates moves, renames, and archiving with explicit user approval
- Identifies obsolete files likely no longer needed
File Organizer by the numbers
- 1,026 all-time installs (skills.sh)
- +20 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #451 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill file-organizerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1k |
|---|---|
| repo stars | ★ 44k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | sickn33/antigravity-awesome-skills ↗ |
How do you deduplicate and reorganize project files?
Automatically analyze, deduplicate, rename, and intelligently reorganize project files and folders with full approval gates.
Who is it for?
Developers cleaning Downloads, scattered project directories, or pre-archive folders who want agent-proposed organization with explicit approval steps.
Skip if: Repositories requiring automated CI-driven refactors or teams that forbid any agent-initiated filesystem changes without manual scripts.
When should I use this skill?
The user mentions messy folders, duplicate files, Downloads cleanup, reorganizing project structure, or pre-archive file hygiene.
What you get
Approved folder structure, deduplicated files, renamed assets, and removed stale clutter.
- reorganization plan
- deduplication report
- renamed folder structure
By the numbers
- Documents six numbered capability areas including clutter reduction for old files
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
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
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 -rnSummarize 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 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
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
# 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)
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
How it compares
Use file-organizer for interactive folder cleanup with approvals; use git-based refactor tools when changes must stay inside version-controlled code moves only.
FAQ
Does file-organizer move files without permission?
No. file-organizer analyzes, deduplicates, renames, and reorganizes with full approval gates. The agent proposes changes and waits for developer consent before applying any filesystem modifications.
When should developers use file-organizer?
file-organizer fits chaotic Downloads folders, scattered project assets, duplicate files wasting space, or pre-archive cleanup. It also helps establish a sensible structure when starting a new project directory.
Is File Organizer safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.