Skill hud setup

Skill apappas1129/claude-skill-hud/skills/skill-hud-setup

One-time setup that wires the Claude Skill HUD status line into the user's global settings.json. Run this once, right after installing the claude-skill-hud plugin, to finish activating the HUD.From its SKILL.md

Install

npx -y skills add apappas1129/claude-skill-hud --skill skill-hud-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, as published. Nobody here has run it

Skill HUD setup

The claude-skill-hud plugin's hooks (which log skill invocations) are already active now that the plugin is installed. The one piece a plugin cannot wire up automatically is the main session status line — that's a plain user-level settings.json field, not a plugin-managed component, so it needs to be written once, explicitly.

This skill's job: add that one statusLine entry, without touching anything else already in the user's settings.

Resolved paths for this install

These paths were substituted into this skill's content when it loaded, so they're already correct for wherever this plugin is installed on this machine:

Plugin root: ${CLAUDE_PLUGIN_ROOT}
Persistent data directory: ${CLAUDE_PLUGIN_DATA}
Status line script: ${CLAUDE_PLUGIN_ROOT}/scripts/statusline.sh

Steps

Read ~/.claude/settings.json. If it doesn't exist, treat it as {}.
Check the existing statusLine key, if any:
- If it's already set to a command containing scripts/statusline.sh from this plugin's root, the HUD is already configured — tell the user this and stop, no changes needed.
- If a different statusLine is already configured (the user has their own custom one), stop and ask the user how they want to proceed. Do not silently overwrite it. Options: replace it, or skip HUD setup and let the user merge it manually.
- If no statusLine key exists, proceed to step 3.
Add this exact block to the settings JSON, merging it in alongside any other existing top-level keys (do not remove or reorder unrelated keys):
```
"statusLine": {
  "type": "command",
  "command": "CLAUDE_PLUGIN_DATA=\"${CLAUDE_PLUGIN_DATA}\" \"${CLAUDE_PLUGIN_ROOT}/scripts/statusline.sh\"",
  "refreshInterval": 2
}
```
The CLAUDE_PLUGIN_DATA=... prefix is required: the main status line runs outside the plugin hook/MCP substitution system, so this is the one place that env var has to be set explicitly rather than relying on automatic injection. refreshInterval is a safety net on top of the normal event-driven refresh (after each assistant message) — it forces a re-render every 2 seconds so the HUD can't visibly linger stale.
Write the updated settings file back, preserving existing formatting and keys as much as possible.
Confirm to the user in one or two sentences that the HUD is active, and mention that a new session (or /statusline reload if supported) is needed for the change to take effect. Also mention how to undo: remove the statusLine key from ~/.claude/settings.json, or run /plugin uninstall claude-skill-hud.

One thing to look at

SKILL.md

Skill HUD setup

Resolved paths for this install

Steps

Keep looking