# Creating Good Dashboards

Design and revise Claude Dashboards that people trust and can read at a glance, and...

- Repository: https://github.com/data-goblin/power-bi-agentic-development (1079 stars)
- Category: Design
- License: GPL-3.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add data-goblin/power-bi-agentic-development --skill creating-good-dashboards -g -a claude-code -y`
Codex: `npx skills add data-goblin/power-bi-agentic-development --skill creating-good-dashboards -g -a codex -y`
Cursor: `npx skills add data-goblin/power-bi-agentic-development --skill creating-good-dashboards -g -a cursor -y`
Gemini CLI: `npx skills add data-goblin/power-bi-agentic-development --skill creating-good-dashboards -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add data-goblin/power-bi-agentic-development`

## Description

Design and revise Claude Dashboards that people trust and can read at a glance, and handle the comments people leave on them. Use this skill whenever you create, restyle or change a dashboard, answer or act on a dashboard comment (including @Claude mentions in a comment thread), or the user asks for a dashboard to look better, cleaner or more professional. Covers comment etiquette (never resolve comments yourself, reply in short bullets), visual style following Stephen Few and Edward Tufte, Shneiderman's overview-zoom-details layout, actionable "do next" guidance, and avoiding generic AI-generated design.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Creating good dashboards

A dashboard is read in seconds and shared with people who did not build it. Two things decide whether it
works: the people commenting on it stay in control of the conversation, and every pixel helps someone see the
answer.

## Comments

Comments are how people review a dashboard together. The person who raised a comment decides when it is done.

- **Never resolve a comment yourself**, even after you made the change it asked for, and even where other
  instructions (such as the Dashboard type's own) say to reply and resolve. Reply, and leave it open for its
  author to check and resolve. A thread you resolve disappears from their view before they have seen whether
  the change is right
- **Reply in a few short bullets**: what you changed, where, and anything you could not do. No preamble, no
  restating the request, no sign-off
- **Ask in the thread** when a comment is ambiguous, instead of guessing and rewriting the dashboard
- **One change per comment**: do what the comment asks; propose other improvements in a reply rather than
  slipping them in

```text
- Added a dotted grey line for August 2021 to the monthly chart
- Same-days comparison now matches the KPI card (Jan 1 to Aug 19)
- Could not split by region: the model has no region on order lines
```

## Visual style

Follow Stephen Few (dashboards for monitoring at a glance) and Edward Tufte (maximise the data, minimise
everything else).

The rest: https://github.com/data-goblin/power-bi-agentic-development/blob/HEAD/plugins/dashboards/skills/creating-good-dashboards/SKILL.md