Dashboard
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.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Dashboard when an AI agent needs a reusable SKILL.md workflow for this job: 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.
When not to use it
Skip Dashboard when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/dashboard # Save SKILL.md to ~/.claude/skills/dashboard/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/dashboard/SKILL.md. For a shared project, commit the folder at .claude/skills/dashboard/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Dashboard skill for this task: Read the active DESIGN.md (injected above). Colors, typography, spacing,. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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.
Intended uses
- Read the active DESIGN.md (injected above). Colors, typography, spacing,
- Classify what the dashboard monitors (sales, traffic, usage, incidents,
- Lay out the required regions:
- Left sidebar (220–260px): brand mark at top, 6–8 nav links with
- Top bar: page title on the left, search input + user avatar / status
- 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
- Row 3: one secondary chart or table (recent events, top items, etc.).
- 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.
- Charts: inline SVG only, no JS libraries. A line chart is 10 lines of
- 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
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.