webup-skills-cc plugin
A Claude Code plugin bundling two skills: a threshold-colored status line and a /buddy companion reroller.
- 134 ★ on the repository
- Last commit
Extended access
Why this level
- The companion-reroll script edits `~/.claude.json` directly, including the user id and, for Pro/Max, a temporary `accountUuid` reset.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/webup-skills-ccDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The companion-reroll script edits `~/.claude.json` directly, including the user id and, for Pro/Max, a temporary `accountUuid` reset.
This is third-party code. Review the repository files before installing.
What it does
webup-skills-cc packages two Claude Code utilities into one plugin. The first, webup-statusline, builds a custom status line: pick columns (model, remaining context, session cost, effort level, worktree, git branch) and a theme, and the context and effort columns recolor by threshold — green, yellow, red. The second, webup-buddy-reroll, targets a specific /buddy companion species and rarity. Claude Code derives the companion deterministically from a user id, so the skill brute-forces candidate ids in `~/.claude.json` until the hash lands on the wanted combination, then renames the companion and sets its personality.
Who it is for. Claude Code users whose default status line says too little about session state, and who want a different /buddy companion than the one they were dealt.
Good fit when
- You want remaining context and session cost visible in the status line without a separate command.
- The effort level changes often, and a color cue on 'high' would help at a glance.
- Work happens across several worktrees at once, and the line should show which one the session is in.
- The current /buddy companion has worn out its welcome, and you want a specific species and rarity instead of random rerolls.
Not a fit when
- No Bun on the machine and installing it for one script is not worth it (the hash comes out wrong without it).
- A Pro or Max account, and setting up the OAuth workaround for the `accountUuid` lock is not worth the trouble.
- The stock Claude Code status line without color thresholds or a theme is already enough.
Example request
Set up a gruvbox status line with context, cost and git branch, then reroll my /buddy companion into a legendary dragon.Limitations
Correct hash brute-forcing needs Bun (`Bun.hash()`); running the script under Node.js produces a different companion than requested. Pro and Max accounts go through a separate OAuth setup first, since `/buddy` there keys off `accountUuid` rather than the freely replaceable `userID`. The status-line generator writes a script to `~/.claude/scripts/statusline.sh` and edits `~/.claude/settings.json`, and colored columns need `jq` installed. A companion or status-line change needs a Claude Code restart to take effect.
How to disable. Remove the plugin with `/plugin uninstall cc-hacks@webup-skills-cc`. The status line itself goes away by deleting `statusLine` from `~/.claude/settings.json` and the `~/.claude/scripts/statusline.sh` file.
FAQ
How do I install webup-skills-cc in Claude Code?
Globally, the simplest way: `npx skills add webup/skills-cc -g`. A single skill installs with `-s`, e.g. `npx skills add webup/skills-cc -s webup-statusline -g`.
Why doesn't the companion reroll give the right result under Node.js?
Claude Code is Bun-bundled and hashes the userID with `Bun.hash()` (xxHash64). Node.js computes a different hash (FNV-1a), so the reroll script must run under Bun, including via `npx -y bun`.
What about Pro or Max subscription accounts?
On those accounts `/buddy` keys off `accountUuid`, not `userID`, so a direct swap does not work. The skill walks through an OAuth setup instead: a token from `claude setup-token` in a separate terminal, a config backup and temporary reset, then restoring it after the reroll.
What makes the context and effort columns different from the rest?
They are the only two columns colored by threshold: green when relaxed, yellow approaching the limit, red near it. Other columns (model, directory, git, worktree) just report a fact with no color logic.
Can I set a custom icon for the effort column?
Yes, with `--effort-icon` and the built-in presets (`arrow`, `bolt`, `flash`, `reason`, `dot`, `none`), or any character you like.
Discussion
No questions or reviews yet.
Related
PluginsThree Claude Code plugins: the savvy-flow orchestrator with tiered subagents and two mods for a progress panel and a cache timer
Nick Tune's plugin marketplace for Claude Code: checks before a task is handed in, code review and TDD personas
A Claude Code plugin that puts context usage, active tools, running subagents and todo progress into the statusline
A set of Claude Code mods: status lines above the prompt, a guard against risky commands and a few small games
A marketplace of eight Claude Code plugins: session memory, research, commits, skill authoring and more.
A set of 24 slash commands for the Claude Code CLI: commits, review, refactoring, tests and cleanup without repeating the same prompts
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| webup-skills-cc (this card) | no | 134 | |
| ccstatusline | no | 13,590 | a standalone CLI for the status line only; webup-skills-cc adds a second function, /buddy companion rerolling, in the same plugin |
| Claude HUD | no | 29,182 | a separate HUD panel plugin; this skill works through the stock status line with no extra interface |
README in short
The author bundled two personal Claude Code hacks into one plugin with a shared marketplace manifest. The README ships in Chinese and Japanese besides English, with screenshots of two status-line themes as examples.