skills/mole-mac-cleanup/SKILL.md
Use when the user asks to clean, optimize, uninstall, inspect disk usage, or purge project artifacts on macOS.
npx skillsauth add bjesuiter/skills mole-mac-cleanupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Repo: https://github.com/tw93/Mole
Command: mo (not mole!)
Install: brew install mole
Note for humans:
mowithout params opens an interactive TUI mode. Not useful for agents, but you might wanna try it manually! 😉
All-in-one toolkit combining CleanMyMac, AppCleaner, DaisyDisk, and iStat Menus:
node_modules, target, build, etc.mo clean --dry-run # Preview cleanup plan
mo clean --dry-run --debug # Detailed preview with risk levels & file info
mo optimize --dry-run # Preview optimization actions
mo optimize --dry-run --debug # Detailed optimization preview
mo clean # Run deep cleanup (caches, logs, browser data, trash)
mo clean --debug # Cleanup with detailed logs
mo optimize # Rebuild caches, reset services, refresh Finder/Dock
mo optimize --debug # With detailed operation logs
What mo optimize does:
mo clean --whitelist # Manage protected cache paths
mo optimize --whitelist # Manage protected optimization rules
mo purge # Clean old build artifacts (node_modules, target, venv, etc.)
mo purge --paths # Configure which directories to scan
Config file: ~/.config/mole/purge_paths
mo installer # Find/remove .dmg, .pkg, .zip installers
Scans: Downloads, Desktop, Homebrew caches, iCloud, Mail attachments
mo touchid # Configure Touch ID for sudo
mo completion # Set up shell tab completion
mo update # Update Mole itself
mo remove # Uninstall Mole from system
mo --version # Show installed version
mo --help # Show help
Check what would be cleaned:
mo clean --dry-run --debug
If looks good, run cleanup:
mo clean
Optimize system (after cleanup):
mo optimize --dry-run
mo optimize
Clean dev project artifacts:
mo purge
mo clean)--dry-run first. Built with strict protections.--debug for detailed logs.testing
Use when the user mentions Clawpatch/clawpatch.ai, semantic feature review, repo-wide AI audit, persistent findings, or clawpatch init/map/review/report/fix/revalidate.
development
Use when the user asks for autoreview, Codex/Claude second-model review, or final review of dirty changes, a branch, commit, or PR before ship.
testing
Use when the user asks to cut, prepare, publish, tag, or verify a release, especially npm/package releases.
tools
Use when adding, writing, fixing, or exposing a script for the Tuna macOS launcher.