claude-slim

# claude-slim — Token Overhead Reducer Analyze the user's Claude Code environment for token waste and perform non-destructive cleanup. ## Subcommands - `/claude-slim` or `/claude-slim run` → full pipeline (scan → propose → execute → report) - `/claude-slim scan` → report only, no changes - `/claude-slim scan --json` → raw JSON output - `/claude-slim doctor` → check scanner prerequisites and session-log signal quality - `/claude-slim restore` → restore previously disabled items --- ## Phase 1 — Scan Run the CLI to collect environment data: ```bash cd "${CLAUDE_PLUGIN_ROOT}" && node dist/cli.js scan --json ``` If `CLAUDE_PLUGIN_ROOT` is not set: ```bash PLUGIN_DIR=$(find ~/.claude/plugins -path "*/claude-slim/dist/cli.js" -type f 2>/dev/null | head -1 | xargs dirname | xargs dirname) cd "$PLUGIN_DIR" && node dist/cli.js scan --json ``` If `node` is not available, fall back to the legacy bash scanner: ```bash bash "${CLAUDE_PLUGIN_ROOT}/skills/claude-slim/scripts/scan.sh" ``` --- ## Phase 2 — Interpret & Present After getting the scan JSON, YOU must interpret and present results to the user. Do NOT just dump raw CLI output. Present a full diagnostic report in the user's language. > **Templates below are shown in English for readability. Always translate headers, labels, and prompts into the user's detected language when rendering.** ### 2-1. Environment Snapshot Table Show a summary table: | Item | Count | Tokens | |------|-------|--------| | Local skills | N (XK...