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) and visual style following Stephen Few and Edward Tufte.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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 are how people review a dashboard together. The person who raised a comment decides when it is done.
- 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
Follow Stephen Few (dashboards for monitoring at a glance) and Edward Tufte (maximise the data, minimise everything else).
one screen: the whole answer fits one view without scrolling; a headline sentence states it
hierarchy: most important number top left; KPIs first, then trends, then breakdowns, then detail
kpis: each KPI shows its value, a target and a trend (sparkline), and says the period and unit
data-ink: no 3D, no shadows, no gradients, no heavy borders or boxes; light gridlines or none
colour: greys for context, one accent colour for what needs attention; red and green only for status,
and never as the only signal (colour blindness)
labels: label lines and bars directly; drop legends where a direct label works
charts: bars and lines over pies, gauges and donuts; bullet graphs over gauges for value against target;
sorted bars for rankings; small multiples over one cluttered chart
scales: bar axes start at zero; same scale across small multiples; no dual axes
numbers: round to what the reader needs (2.3M, not 2,312,947.21); align right; use the model's formats
text: plain titles that say what the chart shows ("Late penalties by territory, 2025 YTD")
interaction: every visual crossfilters the others; show active filters and a way to clear them
honesty: mark partial periods, state missing targets, and say when a number is a dashboard-only
calculation rather than a model measure
Before sharing, look at the dashboard as its reader would: can they say in five seconds whether things are on track, and where to look next? If not, remove something before adding anything.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Automatically invoke this skill whenever the user asks about Fabric tenant settings or Power BI tenant settings or auditing tenant settings. You can use this skill if the user mentions "Fabric administration".
The English summary is being prepared. Showing the original description.
Interactive BPA rule generation for Power BI semantic models; guided discovery, model investigation, and expert rule authoring. Automatically invoke when the user mentions "BPA rule", "Best Practice Analyzer", or asks to "create a BPA rule", "audit BPA rules", "recommend BPA rules", "set up BPA for my team", "check model for best practices", "validate BPA rules", "improve a BPA expression".
The English summary is being prepared. Showing the original description.
Writing and executing C# scripts and macros against Power BI semantic models using Tabular Editor 2/3. Automatically invoke when the user mentions "C# script", "Tabular Editor script", "TOM scripting", "MacroActions.json", "XMLA", or asks to "automate model changes", "bulk update measures", "create calculation groups", "write a macro", "format DAX expressions", "manage model metadata".
The English summary is being prepared. Showing the original description.
TOM and ADOMD.NET guidance via PowerShell for connecting to Power BI Desktop's local Analysis Services instance. Covers model enumeration, DAX queries, metadata modification, annotations, calendar definitions, field parameters, query tracing, DAX library package management (daxlib.org), and the Desktop Bridge for reloading and screenshotting the report canvas. Automatically invoke when the user mentions "Power BI Desktop", "Analysis Services port", "TOM", "ADOMD", "daxlib", "DAX library", "DAX UDF package", or asks to "connect to PBI Desktop", "query PBI Desktop with DAX", "modify PBI Desktop model", "add a measure to PBI", "capture visual queries", "create a field parameter", "validate DAX", "intercept DAX queries", "install daxlib", "add DAX SVG", "add IBCS", "reload the report canvas", "screenshot a report page", "Desktop Bridge", or to work with the model and report in Power BI Desktop together.
The English summary is being prepared. Showing the original description.
Step-by-step workflow for creating complete Power BI reports from scratch using pbir CLI. Covers model discovery, report creation, page layout, theme setup, visual placement, field binding, filtering, formatting, validation, and publishing. Automatically invoke when the user asks to "create a new report", "build a report from scratch", "make a dashboard", "set up a report with KPIs", "create an executive dashboard", "add pages and visuals to a new report".
The English summary is being prepared. Showing the original description.
DAX performance optimization for semantic models. Automatically invoke when the user asks to "optimize DAX", "fix slow DAX", "DAX performance", "tune a measure", "debug a measure", "DAX anti-patterns", or mentions slow queries, server timings, or DAX authoring.
The English summary is being prepared. Showing the original description.