agentleFS
GRIDLOCK-NYCGRIDLOCK-NYC/claude-skills/skills/organize/SKILL.md

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

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

    dashboard

    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

  • ElasticSkill

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

  • genomewalkerSkill

    learn

    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

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

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
  1. Distinctive:

    Never modify or duplicate the sorting logic.

    line 19
  2. Distinctive:

    Use Bash to capture file counts before running the script:

    line 27
  3. Distinctive:

    If all three locations are empty of loose files, report "Nothing to organize — Desktop, Downloads, and home root are clean." and stop.

    line 33
  4. Distinctive:

    Use Bash to run the script and capture new log entries:

    line 37
  5. Distinctive:

    Keep the report short — just filenames and destinations, no full paths for source files

    line 80
  6. Distinctive:

    If any of these are true, add a warning:

    line 84

“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.

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

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

If 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)."
fi

Step 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

  1. Script not found: "~/.local/bin/auto-tidy.sh not found. Cannot organize without it."
  2. Permission denied: "Permission denied running auto-tidy.sh. Check: chmod +x ~/.local/bin/auto-tidy.sh"
  3. Log file missing: Script creates it automatically — not an error, just means first run.

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.