Help us improve
Share bugs, ideas, or general feedback.
From mac-disk-cleaner
Clean up safe Mac cache locations, report how much space was freed, and flag any oversized folders worth reviewing manually.
npx claudepluginhub msapps-mobile/claude-plugins --plugin mac-disk-cleanerHow this skill is triggered — by the user, by Claude, or both
Slash command
/mac-disk-cleaner:mac-cleanupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Clean up safe Mac cache locations, report how much space was freed, and flag any oversized folders worth reviewing manually.
Analyzes local Mac disk usage, validates snapshot completeness, and identifies cleanup candidates. Defaults to dry-run preview and requires explicit approval before any deletion. Useful when disk usage is high or user wants to understand disk growth.
Automates macOS disk cleanup and memory monitoring with Mole-based safety guards and LaunchAgent alerting. Responds to low disk space, kernel panics, and vm-compressor shortages on Apple Silicon.
Identifies and cleans disk hogs like Rust target/, node_modules, Python venvs, git garbage, Docker images, Homebrew caches, and hidden temps. Use when disk space is low or full.
Share bugs, ideas, or general feedback.
Clean up safe Mac cache locations, report how much space was freed, and flag any oversized folders worth reviewing manually.
Use this skill when the user says things like: "clean my Mac", "free up disk space", "clear cache", "my Mac is slow", "running out of space", "Mac cleanup", "disk cleanup", "tidy up my Mac", "ניקוי מק", "פנה מקום", "המק שלי מלא", "nettoyage Mac", "limpiar Mac", or any similar request about freeing storage on a Mac.
Also runs automatically when triggered as a scheduled task.
Work through each phase in order. Communicate with the user in whatever language they used.
Environment note: This skill works in both Claude Code (native Bash tool) and Cowork (Desktop Commander). Use whichever shell execution method is available in your environment to run the bash commands below.
Run these two commands and record the results:
df -h / | tail -1
du -sh \
~/Library/Caches/Google/ \
~/Library/Caches/pip/ \
~/Library/Caches/node-gyp/ \
~/Library/Caches/org.swift.swiftpm/ \
~/.gradle/caches/ \
~/Library/Caches/Homebrew/ \
2>/dev/null
Note the "Avail" column from df as before_avail and record each cache size.
Run each command. If a command fails (permission denied, not found), note it and continue — do not abort.
# Google Chrome disk cache (passwords/history/bookmarks are in Application Support, NOT here — safe to delete)
rm -rf ~/Library/Caches/Google/ 2>/dev/null; true
# npm cache
npm cache clean --force 2>/dev/null; true
# Yarn cache
yarn cache clean 2>/dev/null; true
# pip cache
rm -rf ~/Library/Caches/pip/ 2>/dev/null; true
# Swift Package Manager cache (auto-regenerated on next build)
rm -rf ~/Library/Caches/org.swift.swiftpm/ 2>/dev/null; true
# Gradle caches (auto-regenerated on next build)
rm -rf ~/.gradle/caches/ 2>/dev/null; true
# Homebrew — prefer brew cleanup, fall back to rm
brew cleanup 2>/dev/null || rm -rf ~/Library/Caches/Homebrew/ 2>/dev/null; true
Do NOT touch:
~/Library/Application Support/Google/Chrome — contains passwords, history, bookmarks~/Documents, ~/Desktop, ~/Downloads (contents — only scan, never delete)/System or /Librarydf -h / | tail -1
Capture the new "Avail" value as after_avail. Calculate freed = after_avail − before_avail.
Run these to find large items the user may want to handle manually:
du -sh ~/Desktop ~/Downloads ~/Documents 2>/dev/null
# Top 10 largest items on Desktop
du -sh ~/Desktop/* 2>/dev/null | sort -rh | head -10
# Top 10 largest items in Downloads
du -sh ~/Downloads/* 2>/dev/null | sort -rh | head -10
If any folder or file exceeds 3 GB, flag it as worth reviewing. Do not delete anything — only inform.
Present a clean summary in the user's language. Include:
Keep the report concise. Do not overwhelm — surface the most actionable items only.
See references/safe-cache-locations.md for the full list of Mac cache locations and what's safe to delete.