kpi-dashboard-design

Designs effective KPI dashboards with proper metric selection, visual hierarchy, and data visualization best practices. Use when building executive dashboards, creating analytics views, or presenting business metrics.

1.12x

Quality

70%

Does it follow best practices?

Impact

92%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/kpi-dashboard-design/skills/kpi-dashboard-design/SKILL.md

Quality

Content

61%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.

A compact, well-organized design reference with concrete catalogs and executable CSS, but it restates some general knowledge and lacks an explicit sequenced workflow for actually building a dashboard. No bundle files are present, so progressive disclosure rests on the single-file structure.

Suggestions

Trim or condense the 'Good KPIs are' list and chart-selection table, which restate knowledge Claude already has; keep only non-obvious guidance to lift conciseness.

Add a short numbered build workflow (select KPIs → choose layout → apply visual hierarchy → pick charts → wire interactivity) with a verification checkpoint so a dashboard can be produced step-by-step.

Replace generic 'data visualization best practices' phrasing with one or two specific, non-obvious rules to sharpen actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables and lists, but sections like the KPI-selection framework ('Good KPIs are: Relevant to business goals…') and the chart-selection table restate general knowledge Claude already has, so it could be tightened.	3 / 5
Actionability	It gives concrete, usable reference material—a KPI-by-goal catalog, a chart-by-data-type table, an ASCII layout, and executable CSS classes for visual hierarchy—with only minor gaps in end-to-end build guidance.	4 / 5
Workflow Clarity	The content is organized by topic (selection, layout, design, charts, interactivity, practices) which implies a rough sequence, but there is no explicit build workflow with sequenced steps or validation checkpoints; no destructive/batch operations apply so no lower cap.	3 / 5
Progressive Disclosure	It is a single well-sectioned file with clear headers and no need for external references; at roughly 100 lines it does not meet the under-50-line simple-skill case for a 5, and some reference tables could theoretically be split, leaving minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

78%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.

A well-constructed description with third-person voice, explicit trigger guidance, and a clear distinct niche. It is slightly held back by framing its capabilities as qualities of one design action rather than a list of discrete concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Designs effective KPI dashboards') and lists concrete aspects ('metric selection, visual hierarchy, and data visualization best practices'), but these read as qualities of a single design activity rather than multiple discrete actions, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It explicitly answers both what ('Designs effective KPI dashboards with proper metric selection, visual hierarchy, and data visualization best practices') and when ('Use when building executive dashboards, creating analytics views, or presenting business metrics') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when' clause supplies natural phrases users would say ('building executive dashboards, creating analytics views, or presenting business metrics'), with good but not exhaustive coverage; common synonyms like 'reporting' or 'BI dashboard' are missing.	4 / 5
Distinctiveness Conflict Risk	The KPI/dashboard framing ('executive dashboards', 'analytics views', 'business metrics') carves a fairly distinct niche with minimal conflict risk, though it could overlap slightly with general data-visualization or BI skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Path: plugins/kpi-dashboard-design/skills/kpi-dashboard-design/SKILL.md
Commit: 84802a4

Reviewed: 4 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.