organize
Skill0 starsChanged 7 months agoMITView on GitHub
Run the auto-tidy script to sort stray files from Desktop, Downloads, and home root into organized folders. Reports what was moved and shows remaining state. Use when user says 'organize', 'tidy up', 'sort my files', 'clean desktop', 'clean downloads', or 'organize my files'. Do NOT use for deleting files or emptying trash.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- paulogabriel/beryltheir own version, first seen Nov 8, 2026
- SethGammon/Citadeltheir own version, first seen Nov 4, 2026
- yuryalencar/ai-skillstheir own version, first seen Nov 1, 2026
- zarubinvibe/athenatheir own version, first seen Nov 1, 2026
- snuffish/dotfilestheir own version, first seen Nov 1, 2026
- mcpware/cross-code-organizertheir own version, first seen Oct 25, 2026
Used with
Projects with it also use dashboard, create-skill and 2 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.
GoogleSkilldashboard
Configures and launches the GKE Capacity & Triage Dashboard scoped to a GCP project ID, GKE cluster name, or target ML workload ID. Uses the configure-and-launch-dashboard action and launch-workload-dashboard workflow to verify local dashboard health, discover cluster capacity, trigger live scans, and generate deep-linked URLs. Use when the user types "/dashboard", says "launch dashboard", "open dashboard", "show capacity", or "view triage dashboard" with a project, cluster, or workload. Don't use for general workload log querying or automated failure attribution (use the troubleshoot skill).
Also in 3 projects that use this
ElasticSkillcreate-skill
Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.
Also in 3 projects that use this
genomewalkerSkilllearn
Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 4 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- SethGammon/Citadel★ 927same name
- yunshu0909/yunshu_skillshub★ 760same name
- mcpware/cross-code-organizer★ 385same name
- mcpware/claude-code-organizer★ 383same name
- TyrealQ/q-skills★ 108same name
- sanghun0724/cmux-claude-skills★ 33same name
- seongjaeryu/bindly-claude-code★ 8same name
- mayankjain1815-commits/CITADEL★ 4same name
- zarubinvibe/athena★ 2same name
- ianpugfaced55/claude-code-organizer★ 0same name
4 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 repository21 other files it gives its agents.
- 5x5Skill
- business-planSkill
- chart-forgeSkill
- code-blast-radiusSkill
- code-edgesSkill
- code-preflightSkill
- code-reviewSkill
- code-securitySkill
- hail-marySkill
- plan-capacitySkill
- plan-directionsSkill
- plan-reviewSkill
- postmortemSkill
- research-critiqueSkill
- research-searchSkill
- session-auditSkill
- session-driftSkill
- skill-builderSkill
- skill-evalSkill
- ui-ideasSkill
- update-prSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
6
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 19
Never modify or duplicate the sorting logic.
- Distinctive: line 27
Use Bash to capture file counts before running the script:
- Distinctive: line 33
If all three locations are empty of loose files, report "Nothing to organize — Desktop, Downloads, and home root are clean." and stop.
- Distinctive: line 37
Use Bash to run the script and capture new log entries:
- Distinctive: line 80
Keep the report short — just filenames and destinations, no full paths for source files
- Distinctive: line 84
If any of these are true, add a warning:
“Common” is measured: kept by at least 6 in 10 of the 11 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
Organize
Sort stray files from ~/Desktop, ~/Downloads, and ~/ into organized subfolders using the existing auto-tidy script.
Important
- This skill invokes
~/.local/bin/auto-tidy.sh— all sorting rules live there, not here - Never modify or duplicate the sorting logic; just call the script
- The script moves files older than 30 min in Downloads, older than 24h on Desktop, and immediately from home root
- Name collisions are handled safely by the script (appends timestamp)
Instructions
Step 1: Snapshot before state
Use Bash to capture file counts before running the script:
echo "=== DESKTOP ===" && ls -1 ~/Desktop 2>/dev/null | head -30 && echo "---" && echo "=== DOWNLOADS (loose files) ===" && find ~/Downloads -maxdepth 1 -type f | head -30 && echo "---" && echo "=== HOME ROOT (loose files) ===" && find ~/ -maxdepth 1 -type f -not -name '.*' | head -30If all three locations are empty of loose files, report "Nothing to organize — Desktop, Downloads, and home root are clean." and stop.
Step 2: Run auto-tidy
Use Bash to run the script and capture new log entries:
# Mark log position before run
LOG="$HOME/.local/log/auto-tidy.log"
BEFORE=$(wc -l < "$LOG" 2>/dev/null || echo 0)
# Run the script
bash ~/.local/bin/auto-tidy.sh
# Show only new log lines (what just moved)
AFTER=$(wc -l < "$LOG" 2>/dev/null || echo 0)
if [ "$AFTER" -gt "$BEFORE" ]; then
tail -n +$((BEFORE + 1)) "$LOG"
else
echo "No files were moved (all files may be too recent)."
fiStep 3: Report results
Output a concise summary in this format:
ORGANIZE — [timestamp]
MOVED:
* filename → ~/Downloads/subfolder/
* filename → ~/Documents/work/
...
SKIPPED (too recent):
* [count] files in Downloads (< 30 min old)
* [count] files on Desktop (< 24h old)
AFTER:
Desktop: [count] files remaining
Downloads: [count] loose files remaining
Home root: [count] loose files remaining- Parse the MOVED lines from the log output in Step 2
- For skipped files, compare before counts with moved counts
- Keep the report short — just filenames and destinations, no full paths for source files
Step 4: Flag anything unusual
If any of these are true, add a warning:
- More than 20 files moved in one run → "Large batch — consider checking destinations"
- Files moved from home root → "Home root files moved to ~/Documents/work/ — verify these aren't project files"
- Name collisions occurred (timestamp appended) → "Name collisions detected — timestamped copies created"
Error Handling
- Script not found: "~/.local/bin/auto-tidy.sh not found. Cannot organize without it."
- Permission denied: "Permission denied running auto-tidy.sh. Check: chmod +x ~/.local/bin/auto-tidy.sh"
- Log file missing: Script creates it automatically — not an error, just means first run.
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.

