agentleFS
YangsonHungYangsonHung/awesome-agent-skills/skills/en/mac-software-storage-cleanup/SKILL.md

mac-software-storage-cleanup

Skill18 starsChanged 5 days agoMITView on GitHub

Use when auditing macOS app storage, cleaning priority caches, or recommending reclaimable disk space.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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:

    Use this skill when the user:

    line 14
  2. Distinctive:

    Do not use this skill when:

    line 22
  3. Very specific:

    Run scripts/report_sizes.sh first to inventory install sources and major storage consumers.

    line 29
  4. Very specific:

    Only after explicit user confirmation, run scripts/cleanup_priority1.sh or an equivalent low-risk cleanup action.

    line 36
  5. Very specific:

    After cleanup, recompute usage and show a before -> after -> reclaimed summary.

    line 37
  6. Distinctive:

    Every cleanup action must include before-and-after comparison

    line 62
  7. Distinctive:

    Do not delete priority-2 directories without explicit user approval

    line 63
  8. Distinctive:

    Do not use destructive git commands

    line 67
  9. Distinctive:

    Do not delete unconfirmed application data

    line 68
  10. Distinctive:

    If a script fails, fall back to read-only inspection or the smallest safe cleanup scope

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Mac Software Storage Cleanup

Overview

Audit installed software and storage usage on macOS, produce prioritized cleanup recommendations, and execute low-risk cleanup only after confirmation. The skill separates app inventory, cache cleanup, simulator data, and medium-risk application data so destructive actions remain explicit and reversible where possible.

When to Use

Use this skill when the user:

  • Wants to inspect software installed under /Applications, ~/Applications, Homebrew Formula, or Homebrew Cask
  • Wants storage usage ranked by size across apps and common cache locations
  • Wants to clean low-risk paths such as ~/Library/Caches and ~/Library/Developer/CoreSimulator
  • Wants reclaim recommendations with low-risk and medium-risk cleanup separated clearly

Do not use

Do not use this skill when:

  • The user wants to uninstall one specific app instead of doing storage governance
  • The user asks to delete application data directly without explicit confirmation
  • The environment is not macOS or the target paths do not apply

Instructions

  1. Run scripts/report_sizes.sh first to inventory install sources and major storage consumers.
  2. Classify cleanup candidates by priority:
    • Priority 1: caches and simulator data, generally low risk.
    • Priority 2: application data directories, report only and never delete by default.
    • Priority 3: low-yield small caches or logs.
  3. Reports must show category totals, counts, and Top N largest entries.
  4. To inspect priority-2 candidates, run scripts/list_priority2_candidates.sh [target_dir] [TopN].
  5. Only after explicit user confirmation, run scripts/cleanup_priority1.sh or an equivalent low-risk cleanup action.
  6. After cleanup, recompute usage and show a before -> after -> reclaimed summary.

Workflow

Inventory install sources and storage usage
  -> identify high-value cleanup targets
  -> present prioritized recommendations
  -> wait for user confirmation
  -> run low-risk cleanup
  -> verify reclaimed space

Run commands

bash scripts/report_sizes.sh
bash scripts/list_priority2_candidates.sh ~/Library/Application\\ Support 20
bash scripts/cleanup_priority1.sh

Output requirements

  • Show counts and total size for each path category
  • List Top N largest consumers so the user can decide quickly
  • Every cleanup action must include before-and-after comparison
  • Do not delete priority-2 directories without explicit user approval

Boundaries

  • Do not use destructive git commands
  • Do not delete unconfirmed application data
  • If a script fails, fall back to read-only inspection or the smallest safe cleanup scope

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.