dashboard · nexu-io — Claude Code skill: what it does, how to install
Builds an admin or analytics screen as one HTML file: sidebar, top bar, KPI cards and SVG charts. Fits briefs that ask for a dashboard or control panel.
Apache-2.0 294 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill dashboard -a claude-codeWhat dashboard does
The dashboard skill produces an admin or analytics screen as a single self-contained HTML file. A fixed sidebar (220–260px) holds 6–8 icon links. The top bar carries the page title, a search field and the user avatar. The main area has 3–4 KPI cards showing change against the prior period, then a primary chart and a secondary chart or table.
Before drawing anything, the agent works out from the brief what is being monitored and writes specific metric names and values instead of Metric A placeholders. Charts are inline SVG with no JS libraries: a <polyline> for lines, <rect> elements for bars. Layout runs on CSS Grid, and each region gets a data-od-id attribute so comment mode can target it.
It needs a DESIGN.md. Colors, type and spacing all come from that file, and without one there are no tokens to draw from. The accent color shows up at most twice: the active sidebar item and one chart highlight.
What it helps with
- build an admin screen with a sidebar and top bar in one HTML file
- show KPIs with change against the prior period
- draw line or bar charts as inline SVG, no chart library
- get a prototype with believable metric names instead of placeholders
- put recent events or top items in a table under the charts
Example prompts for the agent
- Use the dashboard skill to make an e-commerce sales analytics screen in one HTML file.
- I need an admin panel for incident monitoring: KPI cards plus a daily chart, colors from DESIGN.md.
- Build a control panel for server load with the dashboard skill.
How to install dashboard
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill dashboard -a claude-code2Manually: put the files in place
~/.claude/skills/dashboard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/dashboard/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill dashboard -a codex2Manually: put the files in place
.agents/skills/dashboard/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill dashboard -a cursor2Manually: put the files in place
.cursor/skills/dashboard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/dashboard/SKILL.md2Manually: put the files in place
.github/skills/dashboard/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill dashboard -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/dashboardManually: put the files in place
.devin/skills/dashboard/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill dashboard -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about dashboard
How do I install dashboard in Claude Code?
Run npx skills add nexu-io/open-design --skill dashboard -a claude-code. The skill file sits at ~/.claude/skills/dashboard/SKILL.md.
What does dashboard do?
It generates a one-screen admin page with a sidebar, top bar, KPI cards and SVG charts. The agent returns it as an HTML document inside an <artifact> block.
Does dashboard need a DESIGN.md?
Yes. The skill reads the active DESIGN.md for colors, typography, layout and component styling, and does not invent its own tokens.
Source text
SKILL.md · Apache-2.0
---
name: dashboard
description: |
Admin / analytics dashboard in a single HTML file. Fixed left sidebar,
top bar with user/search, main grid of KPI cards and one or two charts.
Use when the brief asks for a "dashboard", "admin", "analytics", or
"control panel" screen.
triggers:
- "dashboard"
- "admin panel"
- "analytics"
- "control panel"
- "后台"
- "管理后台"
od:
mode: prototype
platform: desktop
scenario: operations
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
craft:
requires: [state-coverage, accessibility-baseline, laws-of-ux]
---
# Dashboard Skill
Produce a single-screen admin / analytics dashboard.
## Workflow
1. **Read the active DESIGN.md** (injected above). Colors, typography, spacing,
component styling all come from it. Do not invent new tokens.
2. **Classify** what the dashboard monitors (sales, traffic, usage, incidents,
ops, etc.) from the brief. Generate specific, plausible metric names and
values — no "Metric A / Metric B" placeholders.
3. **Lay out** the required regions:
- **Left sidebar** (220–260px): brand mark at top, 6–8 nav links with
icons, active state uses the DS accent.
- **Top bar**: page title on the left, search input + user avatar / status
on the right.
- **Main**:
- Row 1: 3–4 KPI cards (label + big number + delta vs. prior period).
- Row 2: one primary chart (full width or 2/3) — render as an inline SVG
line / bar / area chart drawn from real-looking numbers.
- Row 3: one secondary chart or table (recent events, top items, etc.).
4. **Write** one self-contained HTML document:
- `<!doctype html>` through `</html>`, CSS in one inline `<style>` block.
- CSS Grid for the overall layout; Flexbox inside cards.
- Semantic HTML: `<aside>`, `<header>`, `<main>`, `<section>`.
- Tag each logical region with `data-od-id="slug"` for comment mode.
5. **Charts**: inline SVG only, no JS libraries. A line chart is ~10 lines of
`<polyline>` with a subtle area fill. A bar chart is N `<rect>`s with
DS-accent fill. Label axes lightly (muted text, smaller scale).
6. **Self-check**:
- Every color comes from DESIGN.md tokens.
- Accent used at most twice (sidebar active + one chart highlight).
- Sidebar + top bar are sticky; main scrolls independently.
- Density matches the DS mood — airy DSes get more padding, dense DSes
(trading, crypto) tighten rows.
## Output contract
Emit between `<artifact>` tags:
```
<artifact identifier="dashboard-slug" type="text/html" title="Dashboard Title">
<!doctype html>
<html>...</html>
</artifact>
```
One sentence before the artifact, nothing after.
© nexu-io · Apache-2.0 · nexu-io/open-design
Similar skills
All skills for Frontend and UI →dashboard by other authors comes first.