system
/system
Scan the whole machine for space outside project folders: tool caches, Xcode simulators, Android emulators, Docker or Colima volumes, app caches. Use when asked why the whole disk is full or what System Data or Docker space is. Read-only; tiers each item SAFE, VERIFY or KEEP. macOS only.
- Author
- jwill824 ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 05.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Scan the whole machine for space outside project folders: tool caches, Xcode simulators, Android emulators, Docker or Colima volumes, app caches. Use when asked why the whole disk is full or what System Data or Docker space is. Read-only; tiers each item SAFE, VERIFY or KEEP. macOS only.
Arguments
/system [--html FILE] [--save-state]
Original author description
Scan the whole machine for space outside project folders: tool caches, Xcode simulators, Android emulators, Docker or Colima volumes, app caches. Use when asked why the whole disk is full or what System Data or Docker space is. Read-only; tiers each item SAFE, VERIFY or KEEP. macOS only.
How it works
- Next steps
- Notes
SKILL.md preview
---
name: system
description: Scan the whole machine for space outside project folders: tool caches, Xcode simulators, Android emulators, Docker or Colima volumes, app caches. Use when asked why the whole disk is full or what System Data or Docker space is. Read-only; tiers each item SAFE, VERIFY or KEEP. macOS only.
argument-hint: "[--html FILE] [--save-state]"
---
# system
Plugin root: `${CLAUDE_PLUGIN_ROOT}`. Scripts are in `${CLAUDE_PLUGIN_ROOT}/scripts/`; shared guidance is in `${CLAUDE_PLUGIN_ROOT}/references/`.
This skill only looks. It removes nothing, and it cannot: removal belongs to `/disk-reclaim:run` and `/disk-reclaim:review`, which the user starts by typing them.
Read `${CLAUDE_PLUGIN_ROOT}/references/tiers-and-gates.md` before presenting: each item carries a tier, an activity class and the gates that ran.
When the question is about the whole machine ("why is my disk full", "what is the System Data / Docker / simulator space"), run the system scanner instead of pointing `scan.py` at the home folder:
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/scan_system.py [--html "$(mktemp -d)/report.html"] [--json] [--min-mb 100] [--active-days 7] [--stale-days 30]
```
Pass the user's arguments (`$ARGUMENTS`) through. Add `--save-state` to feed `/disk-reclaim:status`. Read-only, about a minute. It reports tool caches, Xcode and simulators, Android emulators, Docker/Colima, `~/.claude` data and `~/Library/Caches`, with bar charts, a tier by activity matrix and, with `--html`, a self-contained treemap page (open it locally; publish it as an Artifact only if the user asks, since item names can reveal customer or project names). Tools that are not installed are skipped and noted.
Present SAFE in three groups: stale (reclaim freely), recently used (reclaimable, but the user will feel the rebuild) and blocked right now (say what holds it, for example live `uvx` processes holding the uv cache lock). Docker commands list explicit images, containers and volumes with an age floor and no `-f`, so what was reviewed is what runs. Sizes come from the tool's own dry run where one exists (`brew cleanup -n`) and carry a `~` when they are an upper bound.
## Next steps
Tell the user what to type next, since you cannot start these yourself:
- **SAFE items:** `/disk-reclaim:run` (dry run first, then execute after approval).
- **VERIFY items:** `/disk-reclaim:review` (a decision per group; remembers what they keep).
## Notes
- **Platform.** The machine-wide scan is macOS-only and exits with a message elsewhere. Each tool in the scan (Xcode, Docker or Colima, Android, uv, pnpm, Homebrew) is skipped when it is not installed. It needs `lsof` and `ps`: every SAFE item is held if `lsof` fails.
- Standard library Python 3 only.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jwill824/claude-plugins | 100 | MIT |
| virtualian/pai | 95 | MIT |
Database snapshot: 13.11.2026 · package version 6878c52f633e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100pro-disk-cleanup
Find and clear reclaimable disk space safely on any macOS, Windows or Linux machine and stack: read-only scan, three tiers (safe, decide, keep), closed-issue worktrees with backup, build output, caches, Docker. Use for 'disk is full', 'free up space'. - 90free-up-disk-space
Free up disk space on the user's Mac safely with DiskSpace AI. Use when the user says their Mac or disk is full, asks what's taking up space, can't install a macOS update, wants to clean caches, Xcode DerivedData, simulators, Docker, node_modules or AI models, or asks whether a… - 100mac-disk-cleanup
Free up disk space on a Mac safely. Surveys what is using storage in about a minute without walking the whole disk, proposes what can go with sizes and consequences, lets the user pick, removes it with each tool's own commands, and reports the space freed. Covers Xcode… - 98disk-cleanup
Find what is eating disk space on macOS, Linux, or Windows and propose what can be safely deleted: tool caches, Xcode/simulator data, unused Docker images and volumes, dependency folders (node_modules, .venv, target, Pods, vendor) of projects that have been idle for a while, and… - 100scan
Break down how much space a project folder or directory uses and which of it can be safely reclaimed (node_modules, build output, caches, logs, git worktrees). Use when asked why a folder or project is huge, how to free up space in it, or whether something in it is safe to… - 100disk-cleanup
Audit and reclaim disk space on macOS with cold-first replacement-cost classification and guarded safe, extra, and deep inventories. Use when disk space is low, builds fail with no-space errors, or the user asks to inspect, clean, prune, or remove caches, temporary files, Docker…