agentleFS
Cor-IncorporatedCor-Incorporated/claude-code-skills/skills/file-organizer/SKILL.md

file-organizer

Skill5 starsChanged 2 months agoMITView on GitHub

Organizes files and folders by analyzing content, detecting duplicates, and restructuring directories. Use when the user says: 'organize my files', 'clean up downloads', 'find duplicates', 'restructure folder', 'organize photos', 'desktop cleanup', 'sort files', 'archive old projects', 'folder structure'. Handles Downloads cleanup, duplicate detection, project reorganization, and photo sorting. Do NOT use for code refactoring (use senior-fullstack), git operations, or codebase restructuring within a software project.

70 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • ArogyaReddySkill

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

  • ArogyaReddySkill

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

  • guaderramaSkill

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

  • trendinuxSkill

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

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before touching any files, confirm with the user:

    line 15
  2. Distinctive:

    All file paths with sizes and modification dates

    line 40
  3. Distinctive:

    Wait for explicit approval before proceeding.

    line 65
  4. Distinctive:

    Stop and ask if anything unexpected occurs

    line 83
  5. Very specific:

    Remove download artifacts: doc-final-v2 (1).pdf to doc.pdf

    line 114
  6. Distinctive:

    If permission denied: inform user which files need elevated permissions

    line 120
  7. Distinctive:

    If disk full during moves: stop, report progress so far, suggest freeing space first

    line 121
  8. Very specific:

    If filename conflict: append -1, -2 suffix, never silently overwrite

    line 122
  9. Distinctive:

    If EXIF data unavailable for photos: fall back to file modification date

    line 123
  10. Very specific:

    If target directory does not exist: create it with mkdir -p, do not fail silently

    line 124

“Common” is measured: kept by at least 6 in 10 of the 63 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

File Organizer

Organize files and folders with analysis, duplicate detection, and automated cleanup.

Workflow

1. Clarify Scope

Before touching any files, confirm with the user:

  • Target directory (Downloads, Documents, Projects, etc.)
  • Goal (find duplicates, restructure, archive old files)
  • Files/folders to exclude (active projects, sensitive data)
  • Aggressiveness (conservative sort vs. comprehensive cleanup)

2. Analyze Current State

ls -la [target_directory]
du -sh [target_directory]/* | sort -rh | head -20

Summarize: total files, file type breakdown, size distribution, obvious issues.

<important if="finding duplicate files or cleaning up redundant copies">

3. Detect Duplicates (When Requested)

# Find exact duplicates by hash
find [directory] -type f -exec md5 {} \; | sort | uniq -d

For each duplicate set, show:

  • All file paths with sizes and modification dates
  • Recommendation on which to keep (newest or best-named)

CRITICAL: Always ask for confirmation before deleting any file.

</important><important if="proposing a file organization plan or restructuring a directory">

4. Propose Organization Plan

Present the plan as a structured summary before executing:

Current: X files across Y folders, Z GB total
Proposed structure:
  [Directory tree]
Changes:
  - Create: [new folders]
  - Move: [file counts per destination]
  - Rename: [patterns]
  - Delete: [duplicates/trash, with user approval]
Files needing your decision: [list unclear items]

Wait for explicit approval before proceeding.

</important><important if="executing file moves, renames, or deletions during cleanup">

5. Execute

mkdir -p "path/to/new/folders"
mv "old/path/file.pdf" "new/path/file.pdf"

Rules:

  • Never delete without confirmation
  • Log all moves for potential undo
  • Preserve original modification dates
  • Handle filename conflicts (append suffix, never overwrite)
  • Stop and ask if anything unexpected occurs
</important>

6. Report Results

After completion, provide:

  • Files organized count
  • Space freed (if duplicates removed)
  • New folder structure tree
  • Maintenance tips (weekly sort, monthly archive review)
<important if="organizing Downloads folder or cleaning up desktop files">

Common Patterns

TaskSuggested Structure
Downloads cleanupWork/, Personal/, Installers/, Archive/, ToSort/
Photo organizationYYYY/MM-MonthName/ (based on EXIF or mtime)
Project restructureActive/, Archive/YYYY/, Templates/
Desktop cleanupMove everything to Documents/ with proper categorization
</important><important if="renaming files or standardizing file naming conventions">

Naming Conventions

  • Files: YYYY-MM-DD-description.ext for dated files
  • Folders: lowercase with hyphens (client-proposals, not Client Proposals)
  • Remove download artifacts: doc-final-v2 (1).pdf to doc.pdf
</important>

Error Handling

  • If permission denied: inform user which files need elevated permissions
  • If disk full during moves: stop, report progress so far, suggest freeing space first
  • If filename conflict: append -1, -2 suffix, never silently overwrite
  • If EXIF data unavailable for photos: fall back to file modification date
  • If target directory does not exist: create it with mkdir -p, do not fail silently

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.