mac-power-tools_skill

Overview

This skill bundles essential macOS power-user utilities into a single toolset focused on safe system cleanup and secure Android file transfer. It aims to speed routine maintenance while preventing accidental data loss by defaulting to dry-run and overwrite checks. The tools are lightweight and scriptable for inclusion in developer workflows.

How this skill works

The cleanup component scans common macOS locations (Trash, ~/Library/Caches, Downloads) and lists candidates based on age rules, using a dry-run by default. The transfer component uses ADB to push files to a connected Android device and verifies integrity by comparing SHA256 checksums on both ends, with checks to avoid accidental overwrites unless forced.

When to use it

• When reclaiming disk space from old downloads, caches, and Trash without risking immediate deletion.
• Before creating disk usage reports or scheduling periodic maintenance tasks.
• When installing or testing Android builds and you need secure, verifiable transfers to a device.
• When automating CI/CD steps that include device-side deployment and verification.
• When you want safe, repeatable cleanup as part of a macOS developer workstation routine.

Best practices

• Run cleanup without --force first to review proposed deletions, then rerun with --force to apply.
• Back up important files externally before running forced cleanup on shared or system directories.
• Confirm the target Android device is the intended device before transferring, especially when multiple devices may be connected.
• Use the --dest option to place builds in a predictable remote path and avoid manual moves on device.
• Integrate commands into scripts with logging to keep an audit trail of actions and checksum verifications.

Example use cases

• Perform a dry-run cleanup weekly to see what would be removed, then execute with --force monthly.
• Push a release APK to /sdcard/Builds/ from your build server and automatically verify checksums before testing.
• Include cleanup as a pre-commit hook on a build machine to remove stale artifacts that inflate disk usage.
• Automate transfer and verification in a CI pipeline step that deploys test builds to a physical device.
• Run cache cleanup on a dev laptop before disk cloning or creating system snapshots.