ops-speeduplisted

## Runtime Context Before scanning, load: 1. **Preferences**: `cat ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` — read `timezone` for timestamps # OPS > SPEEDUP — System Optimizer ## Architecture The `bin/ops-speedup` binary is the single source of truth for probes AND actions. This skill's job is to: 1. Call the binary with the right flags based on user intent 2. Parse the JSON 3. Present a health score + cleanup report 4. Confirm destructive actions per plugin Rule 5 5. Invoke the binary's clean/deep/aggressive modes to execute ## CLI Reference — `bin/ops-speedup` | Command | Purpose | Side effects | |---------|---------|--------------| | `ops-speedup` | Visual banner + hardware summary | None | | `ops-speedup --json` | Quick JSON diagnostics (disk/mem/net only) | None | | `ops-speedup --scan` | Full parallel probe: disk + mem + CPU hogs + power hogs + GPU/ANE + startup | None | | `ops-speedup --clean` | Safe cleanup: caches, tmp, logs, demote daemons, DNS flush, kernel tune | Non-destructive | | `ops-speedup --deep` | `--clean` + Trash, DerivedData, simulators, animation cuts, launch-agent kill | Removes files | | `ops-speedup --aggressive` | `--deep` + unload launch agents, docker `--volumes`, stale `node_modules` (>14d), TCP BBR | Potentially breaking — confirm first | All modes: - Auto-detect OS (macOS / Linux / WSL / Windows) and dispatch OS-specific ops - Idempotent — skip DerivedData/Metro/journal if last run was