usage-dashboardlisted

Use when the user explicitly asks to regenerate, rebuild, or refresh the `claude-prospector` token-usage dashboard with no interpretive question attached — runs `python -m claude_prospector dashboard`, writes the HTML file, and reports the output path. Do NOT use when the user is asking what the data means, where their budget stands, or what to change (use `usage-analysis` instead — it regenerates as part of answering). Trigger phrases: "regenerate the usage dashboard", "rebuild my claude-prospector dashboard", "refresh the token dashboard", "regen the prospector dashboard".
glitchwerks/claude-prospector · ★ 1 · Data & Documents · score 67

Install: claude install-skill glitchwerks/claude-prospector

## Prerequisites This skill invokes `python -m claude_prospector` under the hood. The Python package must be installed in the environment Claude Code uses. See the [README install steps](https://github.com/glitchwerks/claude-prospector#install-as-a-claude-code-plugin) for the two-step install. # Usage Dashboard Skill You are regenerating the `claude-prospector` interactive HTML token-usage dashboard for the user. The user triggered this skill explicitly — produce the dashboard and report the output path. **Do not interpret the data.** The conversational analysis path lives in the `usage-analysis` skill; this skill is the bare "regenerate the file" surface. ## Companion skill For interpretation (budget status, top consumers, recommendations), point the user at `usage-analysis` instead. If the user's request mixes "rebuild the dashboard" with "and tell me what's happening", run this skill first to refresh the file, then hand off to `usage-analysis` for the analysis pass. ## Default behavior If the user passes no arguments, regenerate against the **full aggregated session history** and write the dashboard to a known path. Pass `--no-open` so the file lands at the known path without spawning a browser tab — that side effect is usually unwanted from inside a Claude Code session. When `$CLAUDE_PLUGIN_DATA` is set (the normal plugin context), the CLI automatically defaults `--output` to `$CLAUDE_PLUGIN_DATA/dashboard.html` and creates the parent directory if needed — you can