mole-mac-cleanup

What This Skill Does

The mole-mac-cleanup skill provides an interface to Mole (mo), a powerful command-line toolkit for macOS system maintenance. It functions as an all-in-one suite that mimics the capabilities of popular graphical utilities like CleanMyMac, AppCleaner, and DaisyDisk. The skill enables automated system hygiene, allowing agents to perform deep cleaning of caches, logs, and browser leftovers, as well as complex system optimizations such as rebuilding Spotlight indices, resetting network services, and refreshing the Finder. Additionally, it features a project-specific artifact purge utility, perfect for clearing out bulky node_modules, target, or venv directories, making it an essential utility for developers and power users alike.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/bjesuiter/mole-mac-cleanup

Ensure that the Mole CLI is installed on your host system via Homebrew: brew install mole

Use Cases

This skill is ideal for scenarios requiring automated system maintenance or pre-deployment environment cleanup. Common use cases include:

• Reclaiming disk space before a large project build.
• Resolving system sluggishness or application unresponsiveness through system-level optimization.
• Removing bloated installer files (.dmg, .pkg) that have accumulated in the Downloads folder.
• Automating the removal of stale build artifacts in development directories.
• Ensuring the system environment is clean after heavy research or data processing tasks.

Example Prompts

1. "Check how much space I can reclaim by running a deep cleanup and show me the details of what will be removed."
2. "Perform a system optimization to refresh the Finder and rebuild my Spotlight index."
3. "Run a purge on my development directories to remove outdated project artifacts like node_modules and target folders."

Tips & Limitations

• Always Dry-Run: Always execute commands with the --dry-run flag first. This allows the agent to inspect the proposed changes before permanently deleting system or project files.
• Debug Mode: For complex issues, append the --debug flag to your command to receive granular details about risk levels and specific file paths being targeted.
• Interactive Mode: Note that the raw mo command triggers an interactive TUI which is not compatible with agent workflows. Ensure all commands use the non-interactive flags documented here.
• Permissions: Some deep system optimizations may require elevated privileges. Ensure your agent environment is configured correctly to handle sudo operations, potentially via mo touchid for convenience.