claude-statusline-beautylisted

# statusline-beauty A multi-line status line for Claude Code, packaged so it installs and updates itself. ``` ✨ Opus 5 | 📁 my-project +173 -104 | 🧩 5 skills | 🤖 2 agents | 🔌 4 mcp | 🔧 87 tools 🌿 $1.77 | 📅 ~$41.20/mo · 9.8Mtok/mo | ♻️ 12 turns | 💲$0.02/turn | 📀 cache HR 80% 🌐 main | ↑2 | ± 3 files | 4h 🟡 ctx [████████████████░░░░░░░░░] 67% · 670k/1M in:26.8k out:127.8k ⚠️ 500k+ 🟢 5h [█████░░░░░░░░░░░░░░░░░░░░] 23% · resets 3h 12m (07:45 PM) ⚪ week [██████████░░░░░░░░░░░░░░░] 41% ⚪ CPU [██████░░░░░░░░░░░░░░░░░░░] 27% · load 0.80 ⚪ RAM [████████░░░░░░░░░░░░░░░░░] 32% · 7.3G free/disk 133G free Claude Code v2.1.220 (LTS) · session_id: a1b2c3d4-e5f6-7890-abcd-ef1234567890 ``` All the real work lives in `scripts/manage.sh`. Do not hand-edit `settings.json` or copy the script around manually — the script handles backups, validation and rollback that ad-hoc edits would skip. ## Example prompts Four different requests map onto different subcommands — don't collapse them into one mental model, each has a different effect: | The user says | Run | Notes | |---|---|---| | `/claude-statusline-beauty` with nothing installed | `manage.sh install` | Checks the latest GitHub release first, so a fresh install lands on the newest version, not whatever this skill checkout happens to bundle. | | "update the status line" | `manage.sh update` | Pulls the **latest published release only** — never `main` directly (see Platform support