Agent skill · daymade
macos-cleaner
Diagnoses and safely reclaims macOS disk space: caches, logs, app remnants, large/duplicate files, Docker/OrbStack, Chromium code-sign clones, developer caches. Use when a Mac is low on storage, shows “Caching needs more space”, or before deleting anything to avoid data loss. Not for Windows/Linux or permission issues (use macos-permissions).
What it needs
About 12k tokens when loaded.
What this skill does
macOS Cleaner Diagnose the actual source of disk pressure, reclaim only approved space, and prove that the cleanup did not damage user data or co-resident services. Entry router Choose the narrowest path that can answer the request: User signal Route --- --- Move selected cold data to an SD card or external disk while retaining its original entry Read external cold archives before copying; bind volume identity, pilot metadata fidelity, verify the retained copy and test original-path consumption before retiring the internal payload Identical inactive local files must retain every path and offline availability Read references/apfs-shared-blocks.md; use only authorized explicit pairs, native APFS checks and the bundled guarded executor Apple Content Caching, AssetCacheManagerUtil, CacheUsed, ActualCacheUsed, iCloud cache, or “Caching needs more space” Read references/applecontentcaching.md completely before probing or proposing commands Docker, OrbStack, images, containers, or volumes Read references/dockeranalysis.md; inspect every object and never use prune-family commands Docker build cache Measure with docker builder du; this skill reports it but does not delete it because Docker exposes category-wide prune controls rather than per-record intent Cargo target trees or manual CI outputs Read references/cleanuptargets.md → Cargo and manual CI outputs before selecting files; requested test executables and unknown results can live inside dependency-named directories Chrome, ChromeDriver, Playwright, Codex Computer Use, Edge, or Chromium has large .codesignclone directories Read references/chromiumcodesignclones.md completely; use the bundled analyzer to separate active, inactive, and unknown exact children and never equate du with physical release A named cache, directory, application, or service is already the suspect Inspect that target first and read the matching semantics in references/cleanuptargets.md; do not start a home-directory or whole-disk scan The user asks …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/macos-cleaner--6872af