Agent skill · daymade
macos-cleaner
Diagnoses and safely reclaims macOS disk space. Use when a Mac is low on storage, reports “Caching needs more space,” shows large Apple Content Caching or AssetCacheManagerUtil usage, or needs analysis of caches, logs, application remnants, large or duplicate files, Docker or OrbStack, Chromium code-sign clones, Homebrew, npm, pip, Xcode, and other developer storage. Routes known suspects to targeted read-only diagnosis before broad scans, distinguishes nominal path accounting from physical release, requires an impact-and-recovery plan plus explicit confirmation before state changes, and verifies disk space and co-resident services afterward.
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 --- --- 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 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 source is genuinely unknown Use the general analysis workflow below; Mole is optional, not the universal first step User-provided scope exclusions override every generic scan suggestion. Do not inspect personal directories, credentials, databases, application state, or unrelated services when the user excludes them. Safety and authorization contract 1. Separate observation from mutation. Complete a read-only diagnosis first. Do not delete, stop a service, edit settings, install or upgrade tools, or run a cleanup preview that may mutate state during that phase. 2. Confirm the exact target. On a remote Mac, record the current host identity before any other work. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/macos-cleaner--6872af