Skip to content

NEXPACE-Limited/msu-skills / plugins/msu-statusline/skills/msu-statusline-install

msu-statusline-install

Verified

Claude Code only — a status line is a Claude Code concept and this skill does nothing on another CLI. Puts the newest MSU Builder notice in the Claude Code status line, and repairs it. Use when the user asks to install, enable, set up, re-install or repair the MSU status line, wants MSU notices or announcements shown under the prompt or in the terminal, or reports that the MSU status line is blank, stale, or gone after an update. Wraps a status line that is already configured rather than replacing it. Taking it back out is `msu-statusline-uninstall`.

FileKindSize
SKILL.mdskill md11.6 KB
references/troubleshooting.mdmarkdown3.4 KB

references/troubleshooting.md

View on GitHub
# When something looks wrong

Each symptom below is what the user actually sees. `CONFIG` is
`${CLAUDE_CONFIG_DIR:-$HOME/.claude}`, and "step 6" is the install's last step, the one
that renders the line in the foreground. The install path is in the skill
body and removal is in `msu-statusline-uninstall`; nothing here changes
`settings.json`.

- **`⚠ board unreachable`.** Polling has been failing for hours and has backed off to
  the polling interval. Usually a network the machine has not had; it clears itself on
  the next successful poll. `curl -sS -o /dev/null -w '%{http_code}\n'
  https://msu.io/builder/notices` says whether the board answers at all.
- **`⚠ notice format changed`.** The board answered and the parser could not read it,
  for hours. This one does not clear itself: the page's shape moved and the plugin has
  to be taught the new one. It is worth reporting — the notice shown, if any, is frozen
  at whatever last parsed. Confirm with
  `bash "${CLAUDE_PLUGIN_ROOT}/tests/test.sh"`, which runs the parser against a captured
  copy of the page: passing there and failing live is exactly this.
- **Blank line, no warning at all.** Check the launcher with `--config` first. A missing
  launcher or failed lookup needs install repair; `NOTICE=off` intentionally prints no
  MSU segment. With notices enabled, inspect `$CONFIG/msu-statusline.cache` and
  `$CONFIG/msu-statusline.cache.failures`: a cold cache after a failed fetch is silent
  until failures reach the warning threshold. Run step 6 for a preview, but a recent
  `.cache.attempted` delays the next request, so repeating it does not force a fetch.
  Check `.statusLine.command` separately; blank stdout does not prove it is miswired.
- **A wrapped status line renders, and the MSU line is simply not there.** The launcher
  is running and the MSU segment produced nothing. Follow the blank-line checks above;
  the previous command's output proves the launcher ran, not that a notice was fetched.
- **`⚠ MSU statusline: plugin not found`.** The launcher walks
  `$CONFIG/plugins/cache/*/msu-statusline/*/` on every render and takes the most recently
  installed one — nothing is cached, so an update is picked up on the next redraw. This
  warning means nothing was found: the plugin is not installed, it is a checkout, or
  `MSU_STATUSLINE_ROOT` is set and points at a directory with no
  `scripts/statusline.sh` in it. That variable wins outright and is never fallen back
  from, so a typo in it produces this warning rather than a working line from somewhere
  else. A status line being wrapped still renders; only the MSU line is lost.
- **Title not clickable.** OSC 8 hyperlinks need a terminal that supports them
  (iTerm2, Kitty, WezTerm, Ghostty). Elsewhere the title still reads normally.
- **A second status line appeared instead of one.** That is `.prev` working as
  intended. To drop the old one, empty `$CONFIG/msu-statusline.prev`.
- **The status line they had before the install stopped rendering.** Read
  `$CONFIG/msu-statusline.prev`. If it names `msu-statusline`, the launcher is refusing
  to replay it on purpose — replaying a command that runs the launcher would recurse
  without bound — and whatever was there was overwritten by an install that mis-read its
  own command as the user's. The file cannot be recovered; put the command back by hand
  if they can name it, and the launcher replays it again from the next redraw.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall