file-organizer
Skill4 starsChanged 4 months agoMITView on GitHub
Organizes a messy folder — proposes a naming convention and folder taxonomy, shows the complete move plan as a dry-run table, executes only after explicit confirmation, and writes an undo.sh before touching anything. Use when the user says "organize this folder", "clean up my Downloads", "sort these files", or "my desktop is a mess". Don't use for deleting or deduplicating files (this skill never deletes) or summarizing file contents (use meeting-notes-actions for notes files).
73 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- SatyaSurisetti/Claude-skillstheir own version, first seen Nov 16, 2026
- darren469/Claude-Skillstheir own version, first seen Nov 16, 2026
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- AlienHub/file-organizertheir own version, first seen Nov 8, 2026
Used with
Projects with it also use meeting-insights-analyzer, skill-share and 10 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.
ArogyaReddySkillmeeting-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 41 projects that use this
ArogyaReddySkillskill-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 27 projects that use this
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 38 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 15 projects that use this
- +8 more from ArogyaReddy
Other versions73 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 73
- ComposioHQ/awesome-claude-skills★ 75ksame name
- NVIDIA/SkillSpector★ 26ksame name
- ComposioHQ/awesome-codex-skills★ 17ksame name
- composio-community/awesome-codex-skills★ 16ksame name
- Prat011/awesome-llm-skills★ 1.7ksame name
- langchain-ai/deepagentsjs★ 1.6ksame name
- Prorise-cool/Claude-Code-Multi-Agent★ 304same name
- smithjoshua/claude-code-cowork-skills-file-organizer★ 57same name
- Amazon-Quick/Amazon-Quick-official-catalog★ 50same name
- ArogyaReddy/ComposioHQ-awesome-claude-skills★ 45same name
63 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 repository74 other files it gives its agents.
- agent-eval-harnessSkill
- context-budget-managerSkill
- incident-rollbackSkill
- memory-hygieneSkill
- model-cost-optimizerSkill
- prompt-debuggerSkill
- skill-author-coachSkill
- third-party-skill-vetterSkill
- api-endpoint-testerSkill
- bug-triage-protocolSkill
- changelog-release-notesSkill
- docs-readme-writerSkill
- env-secrets-hygieneSkill
- github-pr-reviewSkill
- git-ship-flowSkill
- lovable-brief-writerSkill
- supabase-migration-writerSkill
- vercel-deploy-checkSkill
- cold-outreach-sequencerSkill
- competitor-pricing-scanSkill
- contract-redline-scanSkill
- customer-support-inboxSkill
- invoice-runnerSkill
- kpi-dashboard-weeklySkill
- lead-research-dossierSkill
- payment-reconciliationSkill
- pipeline-trackerSkill
- proposal-builderSkill
- stripe-payment-linkSkill
- testimonial-harvesterSkill
- weekly-revenue-reportSkill
- brand-voice-guardianSkill
- case-study-builderSkill
- content-repurposerSkill
- deep-research-briefSkill
- email-nurture-sequenceSkill
- landing-page-copywriterSkill
- linkedin-content-packSkill
- newsletter-assemblerSkill
- seo-blog-writerSkill
- social-listening-reportSkill
- x-thread-builderSkill
- youtube-script-writerSkill
- budget-guardrailsSkill
- ceo-operating-doctrineSkill
- delegation-protocolSkill
- editor-personaSkill
- heartbeat-standupSkill
- hiring-briefSkill
- ops-agent-personaSkill
- researcher-personaSkill
- sales-agent-personaSkill
- support-agent-personaSkill
- weekly-retroSkill
- writer-personaSkill
- calendar-conciergeSkill
- decision-journalSkill
- email-triageSkill
- habit-trackerSkill
- inbox-zero-sprintSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 66 edited versions we read keep these.
1
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 20
Before archiving a finished project or handing a folder to someone else.
“Common” is measured: kept by at least 6 in 10 of the 66 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
Turns a chaotic folder into a clean, documented structure — with a full dry-run plan, an explicit go/no-go, and a working undo.sh written before the first move. The standard: the user sees every single move before it happens, nothing is ever deleted or overwritten, and one command reverses everything.
When to Use
- "Organize my Downloads", "sort this project folder", "impose some order here".
- Before archiving a finished project or handing a folder to someone else.
- Not for: deleting or deduplicating files (this skill never deletes) or summarizing file contents (use
meeting-notes-actionsfor notes files).
Quick Reference
| Action | Command / Call |
| Inventory | find "$DIR" -maxdepth 2 -type f | head -200 and ls -la "$DIR" |
| Profile types | find "$DIR" -maxdepth 2 -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn |
| Collision check | [ -e "$dest" ] && echo "COLLISION: $dest" for every planned destination |
| Create structure | mkdir -p "$DIR/subfolder" |
| Move (never overwrite) | mv -n "src" "dest" — -n is mandatory |
| Undo log | Write undo.sh with one reverse mv -n per move, before any move runs |
Procedure
- Precheck — confirm the target folder exists and count files (
find "$DIR" -maxdepth 2 -type f | wc -l). Over ~300 files: propose organizing the newest or one file-type first. Never operate on/,~itself, or any system/app directory — named subfolders only. - Inventory — profile by extension, size, and modified date. Skim names for natural clusters (invoices, screenshots, drafts, exports). Read-only step: nothing is created or moved.
- Propose the scheme — a taxonomy of 4–8 folders with one-line rules ("Invoices/ — PDFs with invoice/receipt in the name") and a naming convention such as
YYYY-MM-DD_project_description.ext(renames are opt-in — default plan moves only). Get the user's reaction before building the plan. - Build the dry-run table — the FULL move plan, every file, in the template below. No "...and 47 more": every row shown. Check every destination for collisions; on collision, plan a suffixed name (
report_2.pdf), never an overwrite. - Write undo.sh — before anything moves:
undo.shin the target folder, starting#!/bin/sh+ a timestamp comment, then onemv -n "dest" "src"per planned move in reverse order.chmod +x undo.sh. This file exists before the firstmvruns — non-negotiable. - Confirm — state: "{N} moves into {M} folders, 0 deletions, undo.sh ready at {path}. Type yes to execute." Execute only on an explicit yes. Anything else, stop and adjust.
- Execute —
mkdir -pthe folders, then run eachmv -n. If anymvfails or skips (destination existed), record it and continue; report skips at the end. - Report — moved/skipped counts, the new tree (
find "$DIR" -maxdepth 2 -type d), and the undo instruction:sh "$DIR/undo.sh".
Output Template
# Move Plan — {folder} ({N} files) — DRY RUN, nothing moved yet
Proposed taxonomy: {Folder1}/ · {Folder2}/ · ...
Naming convention: {pattern or "keep original names"}
| # | Current name | → Destination | Rule applied |
|---|---|---|---|
| 1 | {file.ext} | {Subfolder}/{file.ext} | {rule} |
| ... every file, no truncation ... |
Collisions handled: {n} (suffixing, never overwriting)
Deletions: 0 (always)
Undo: undo.sh will be written to {folder} BEFORE any move.
Reply "yes" to execute, or tell me what to change.Pitfalls
mvwithout-nsilently overwrites a same-named file — that's data loss with no undo. Every move and every undo line usesmv -n; collisions are resolved by suffixing in the plan, never at execution time by chance.- undo.sh written after the moves (or never) — a crash mid-run then leaves no recovery. Write and
chmod +xundo.sh in step 5, verify it exists (ls -l undo.sh) before the firstmv. If execution halts midway, undo.sh still reverses the completed portion (mv -nmakes re-running it safe). - Plan truncated ("moving 200 files, here are the first 20") — the user can't consent to moves they haven't seen. Show all rows; if the table is unwieldy, that's the signal to shrink scope (one file type or date range per pass), not to hide rows.
- Overreaching scope — hidden files,
.git/,node_modules/, app bundles, or files outside the target folder get swept into the plan. Exclude dotfiles and known system/tooling directories by default; touch only what's directly in the agreed folder. - User says "looks good" to the taxonomy and the agent starts moving — approving the scheme (step 3) is not approving the plan (step 6). Only an explicit yes after the full dry-run table authorizes execution.
Verification
- Dry-run table listed every file (row count == inventory count) before any move
- undo.sh existed and was executable before the first mv ran
- All moves used
mv -n; zero files deleted or overwritten - Post-run: moved + skipped == planned; skips reported by name
sh undo.shwould restore original paths (spot-check 2 lines against the plan)- Nothing outside the target folder was touched
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.

