build-dashboard

Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./data/skills/build-dashboard/SKILL.md

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with comprehensive executable code and a clear workflow, but it is token-heavy: large amounts of standard CSS and template code are inlined rather than split into reference files, hurting both conciseness and progressive disclosure.

Suggestions

Move the full CSS system, Chart.js integration patterns, and performance guidance into separate reference files (e.g., css-reference.md, chart-patterns.md) and link them one level deep from SKILL.md.

Trim or collapse the standard CSS boilerplate (box-sizing, system-font stack, card shadows, responsive media queries) since Claude can already produce this; keep only the project-specific color tokens and layout grid.

Add an explicit validate/retry checkpoint in the workflow (e.g., open the file, check the console for JS errors, fix and re-open) to strengthen the feedback loop.

Dimension	Reasoning	Score
Conciseness	At ~925 lines the body inlines large blocks of standard boilerplate Claude already knows (full CSS color system, layout, KPI, table, and responsive styles, plus a complete base template), making it noticeably verbose with several padded sections.	2 / 5
Actionability	It provides copy-paste-ready, fully executable code for charts (line/bar/doughnut), filters, sortable tables, KPI rendering, CSS, and number formatting, covering the common dashboard cases concretely.	5 / 5
Workflow Clarity	A clear 7-step sequence (Understand, Gather, Design, Build, Implement charts, Add interactivity, Save and open) with a "Confirm it renders correctly" checkpoint; minor validation gaps but no destructive/batch operation requiring a stronger feedback loop.	4 / 5
Progressive Disclosure	Section headers give reasonable structure, but with no bundle files or references, ~925 lines of CSS and chart patterns that clearly belong in separate reference files are inlined directly in SKILL.md.	3 / 5
	Total	14 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, concrete components, and an explicit "Use when" clause covering multiple realistic trigger scenarios. Its main weakness is moderate trigger-term coverage missing synonyms and a file extension.

Suggestions

Add a synonym or file extension (e.g., ".html file" or "browser dashboard") to broaden natural trigger matching.

Consider adding one or two more distinct action verbs beyond "Build" to raise specificity from component-listing to comprehensive action coverage.

Dimension	Reasoning	Score
Specificity	"Build an interactive HTML dashboard with charts, filters, and tables" names concrete components (charts, filters, tables, KPI cards) and the build action, but relies on a single verb with component enumeration rather than multiple distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	It explicitly states what it does ("Build an interactive HTML dashboard with charts, filters, and tables") and gives a concrete "Use when..." clause listing several trigger scenarios, answering both what and when.	5 / 5
Trigger Term Quality	Natural phrases like "executive overview with KPI cards", "shareable self-contained report", "team monitoring snapshot", and "multiple charts with filters" match what users would say, though it lacks synonyms or a file extension (e.g., .html).	4 / 5
Distinctiveness Conflict Risk	"Interactive HTML dashboard" is a clear niche with distinct triggers (KPI cards, executive overview, self-contained report), with only minor overlap risk against generic report/document skills.	4 / 5
	Total	17 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (925 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: anthropics/knowledge-work-plugins
Path: data/skills/build-dashboard/SKILL.md
Commit: 8444efc

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.