creating-good-dashboards — Claude Code skill: setup & guide
creating-good-dashboards enforces visual clarity and comment protocols when building or styling Claude dashboards, applying principles from Edward Tufte, Stephen Few, and Ben Shneiderman.
GPL-3.0 ★ 1,104 updated 2026-10-28
/plugin marketplace add data-goblin/power-bi-agentic-development
/plugin install dashboards@power-bi-agentic-developmentWhat creating-good-dashboards does
This skill guides Claude Code during dashboard design and iteration. Layouts follow Ben Shneiderman's overview-zoom-details pattern: key metrics sit at the top left, time chips replace date pickers, clicking marks triggers cross-filtering, and granular details appear in contextual panels. Visual styling draws directly from Stephen Few and Edward Tufte, prioritizing high data-ink ratios: single-screen views without scrolling, axes starting at zero, direct line labeling, and muted greys accented by a single alert tone.
Strict guidelines govern review threads. Claude must never resolve a comment thread on its own, because doing so hides the discussion before the author checks the result. Instead, it posts short bullet points detailing what changed, mentions limitations, and leaves the resolution to the reviewer.
Without explicit targets supplied by the data model or user, status tags like "on track" are forbidden until compared against prior periods.
What it helps with
- restructure dashboard layouts using Tufte and Few visualization rules
- implement overview, zoom, and detail-on-demand navigation structures
- reply to dashboard review comments without prematurely resolving tickets
- replace generic AI visual aesthetics with domain-tailored charts
Example prompts for the agent
- Clean up this dashboard layout so everything fits one screen without scrolling
- Address the comments on this dashboard, update the visuals, and report changes in bullets
- Add actionable next steps next to each KPI card based on drivers in the data
How to install creating-good-dashboards
1Plugin marketplace
/plugin marketplace add data-goblin/power-bi-agentic-development/plugin install dashboards@power-bi-agentic-developmentThis installs the whole dashboards plugin with all its skills
2Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill creating-good-dashboards -a claude-code3Manually: put the files in place
~/.claude/skills/creating-good-dashboards/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/creating-good-dashboards/
1Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill creating-good-dashboards -a codex2Manually: put the files in place
.agents/skills/creating-good-dashboards/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill creating-good-dashboards -a cursor2Manually: put the files in place
.cursor/skills/creating-good-dashboards/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install data-goblin/power-bi-agentic-development plugins/dashboards/skills/creating-good-dashboards2Manually: put the files in place
.github/skills/creating-good-dashboards/SKILL.md1Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill creating-good-dashboards -a gemini-cli2Platform CLI
gemini skills install https://github.com/data-goblin/power-bi-agentic-development --path plugins/dashboards/skills/creating-good-dashboardsManually: put the files in place
.devin/skills/creating-good-dashboards/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.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 creating-good-dashboards
How to install creating-good-dashboards in Claude Code?
Run these two marketplace commands in order: /plugin marketplace add data-goblin/power-bi-agentic-development followed by /plugin install dashboards@power-bi-agentic-development.
What is creating-good-dashboards?
It is an authoring skill that guides Claude Code to build clean, trustworthy dashboards and handle user feedback without generic AI visual cliches.
Why does the skill forbid resolving comments automatically?
Resolving a thread removes it from the reviewer's view immediately. The skill leaves tickets open so the original author can verify the fix.