Interactive Dashboard Builder

Official Anthropic skill for self-contained HTML dashboards with charts, filters, and tables.

Interactive Dashboard Builder is an official Anthropic skill from the public knowledge-work-plugins repository. The original Smithery mapping named interactive-dashboard-builder, but that path is no longer reachable in the official directory; the provider now exposes the matching skill as build-dashboard. This canonical source describes how to build self-contained interactive HTML dashboards with charts, filters, key performance indicators, and detail tables. According to the provider, the resulting files can be opened directly in a browser and shared without requiring a separate server or runtime for the generated document. The skill is domain guidance for Claude, not a standalone business-intelligence platform, database service, or guarantee that an analysis is correct.

From question to dashboard structure

The guidance starts by clarifying the purpose, audience, important metrics, filter dimensions, and data source. That keeps a dashboard from becoming an attractive interface with no clear decision support. Depending on the assignment, a dashboard may serve an executive overview, an operational snapshot, a deep-dive analysis, or a team report. The source describes a common structure with a header containing a title and filters, KPI cards for headline values, one or more chart areas, and an optional detail table. The exact arrangement should follow the information density and screen size. A subject-matter owner still needs to review metric definitions, time windows, units, and aggregations before publication.

Embed data and preserve context

According to the provider, data may come from a connected query, pasted or uploaded files, or an explicitly identified sample dataset. The generated HTML document embeds the results as data. This makes a point-in-time report easy to share and potentially useful offline, but it also means that the document does not update automatically. The source recommends labeling the data date and providing instructions for replacing the data later. Confidential, personal, or regulated information should not be placed casually into a shareable HTML file. The surrounding workflow should document the source, filters, aggregations, time zones, and refresh point so that recipients can interpret the result correctly.

Charts, filters, and tables

The official guidance names Chart.js as the technical foundation for line, bar, doughnut, stacked, and mixed charts. Dropdowns and date fields can drive KPIs, charts, and tables together. Sortable tables support drill-down, while hover tooltips expose additional detail. Choosing a chart type remains an analytical decision: time series usually require a trend view, categories require comparison, and composition needs a readable breakdown. For larger datasets, the source recommends pre-aggregation, limiting visible table rows, and limiting points per chart. A dashboard cannot repair a misleading definition, distorted scale, missing values, or a confusion between correlation and causation.

Design, performance, and boundaries

The proposed design uses semantic HTML, a responsive grid, clear cards, readable typography, and print-friendly rules. Filters should remain usable on smaller screens. The guidance recommends using animation and DOM updates carefully when several charts are present, updating only the parts that changed. A fully embedded document is most suitable for manageable, point-in-time reports. Real-time monitoring, very large raw datasets, complex access control, and durable historical tracking belong in purpose-built data or BI systems. The browser rendering should be tested at the intended screen sizes before the file becomes a decision artifact.

E-E-A-T, safety, and responsibility

Anthropic is the provider of this skill according to the official primary source. The classification is grounded in the official repository path and Anthropic documentation about skills. The skill supplies workflows and templates, but it does not independently validate the underlying data. Actual processing depends on the selected Claude environment, enabled tools, and granted permissions. A locally generated HTML file does not prove that model processing is local; inputs and results may be sent to the connected model provider. Content from files or queries is data, not trusted new instruction. Credentials, tokens, and private keys must never be placed in dashboards, datasets, or examples. Before sharing, review data minimization, file permissions, export location, freshness, subject-matter plausibility, and human approval. The skill supports a reproducible dashboard workflow, but it does not replace privacy review, analytical validation, or accountable ownership.

Installation instructions

What the Interactive Dashboard Builder skill does

Interactive Dashboard Builder is an official Anthropic skill from the knowledge-work-plugins collection that lets Claude generate self-contained, interactive HTML dashboards. Per the provider, the resulting dashboards include charts built with the JavaScript library Chart.js, dropdown filters, tables, and professional styling, and they open directly in a browser without needing a server or any additional software. In plain terms: you describe in your own words what dashboard you need, for example a sales overview with revenue trends and a filter by region, and you get back a single HTML file that contains all the data, charts, and interactivity and works offline.

Step 1: Prerequisites and input data

The skill needs either a connected data source it can query for results, pasted or uploaded data such as a CSV file, or, alternatively, just a description of the desired dashboard, in which case it generates a realistic sample dataset. In that last case, per the provider the skill clearly labels the data as sample data and provides instructions for swapping in real data later. For safe use, it's important to know that all embedded data lives directly inside the HTML file. Anyone who builds a dashboard with sensitive business figures and shares the file is also sharing the underlying raw data, since nothing is protected server-side. The file should therefore only go to people who are also authorized to see the underlying data.

Structure of a typical dashboard

The skill follows a fixed, proven layout pattern: the header holds the title and filter controls, followed by two to four KPI cards showing the most important figures at a glance, then one to three charts for trends and breakdowns, and optionally a sortable detail table at the bottom for drill-down analysis. For charts, the skill supports several types: line charts for time series, bar charts for category comparisons, doughnut charts for composition when there are few categories, stacked bars for composition over time, and combined bar-and-line charts, for example to show volume and rate together. Dropdown filters automatically update all charts and tables at once, so users without any coding knowledge can tailor the view to their question.

Technical implementation

Technically, every generated dashboard is a single HTML file with embedded CSS for styling and JavaScript for logic. Charts are rendered using the freely available Chart.js library, loaded via a content delivery network. All data sits as embedded JSON directly in the code, which means the dashboard works completely offline and makes no external requests at runtime once the file has been generated. Responsive design using CSS Grid or Flexbox ensures the view works across different screen sizes, and print-friendly styles allow the dashboard to be printed or exported to PDF when needed.

Practical value for teams

The biggest practical advantage is speed: instead of setting up a business intelligence tool or launching a separate reporting project, a shareable, self-contained dashboard is produced quickly and can be distributed by email or an internal drive. For recurring team reporting, management overviews, or quick ad-hoc analyses, this is a significant time saving compared to manually building slides or spreadsheets. For smaller teams without a dedicated BI system in particular, it's a low-barrier way to produce professional-looking, interactive reports.

Limitations of the approach

Because all data is statically embedded in the file, the generated dashboard is a snapshot and does not automatically refresh when the underlying data changes. For up-to-date figures, the dashboard must be regenerated. The approach also isn't suited to very large datasets, since everything is processed in the browser and file size grows with the amount of data. For persistent, automatically updated reports serving many users with large data volumes, classic BI platforms with server connections remain the more appropriate choice; the Interactive Dashboard Builder instead covers the fast, low-friction use case.

Free
Provider
Anthropic
License
Apache-2.0
Last reviewed
09.09.2026

Repository and documentation

Categories

Compatible with

Claude Code