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.
76
64%
Does it follow best practices?
Impact
92%
1.12xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/kpi-dashboard-design/skills/kpi-dashboard-design/SKILL.mdQuality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates both what the skill does and when to use it, with good trigger terms covering natural user language. The specificity around KPI dashboards, metric selection, and visual hierarchy is effective. Minor weakness is potential overlap with broader data visualization or charting skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'metric selection', 'visual hierarchy', and 'data visualization best practices'. Also specifies the output type as 'KPI dashboards'. | 3 / 3 |
Completeness | Clearly 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'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'KPI dashboards', 'executive dashboards', 'analytics views', 'business metrics'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | While 'KPI dashboards' is fairly specific, terms like 'analytics views' and 'data visualization' could overlap with general charting or data visualization skills. The focus on dashboards and business metrics helps but doesn't fully eliminate conflict risk. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a general-purpose reference document about dashboard design rather than an actionable skill for Claude. It covers breadth (KPI selection, layout, visual design, chart types, best practices) but lacks depth in any area—there are no complete executable examples, no clear workflow sequence, and much of the content restates knowledge Claude already has. The ASCII layout diagram is a nice touch but the skill would benefit significantly from concrete implementation examples and a step-by-step workflow.
Suggestions
Add a clear sequential workflow (e.g., 1. Gather requirements → 2. Select KPIs → 3. Design layout → 4. Implement components → 5. Validate with stakeholders) with explicit checkpoints at each stage.
Replace generic reference content (chart selection table, common KPIs list) with complete, executable code examples using a specific framework (e.g., a React dashboard component with Recharts, or a Python Dash/Streamlit dashboard).
Remove sections that explain concepts Claude already knows well (what makes a good KPI, basic chart selection) and focus on project-specific patterns, anti-patterns, and implementation details that add genuine value.
Add a validation step or checklist that Claude can use to verify a completed dashboard meets quality standards before presenting to the user.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes several sections that are general knowledge Claude already possesses (what makes a good KPI, chart selection guidelines, common business KPIs). The lists of best practices and common mistakes are fairly generic and don't add much beyond what Claude would already know. | 2 / 3 |
Actionability | The skill provides some concrete guidance like the ASCII layout diagram and CSS snippets, but overall it reads more like a reference guide than executable instructions. There are no complete, copy-paste-ready code examples for actually building a dashboard (e.g., using a specific framework like React/D3/Plotly), and the CSS is fragmentary rather than part of a working component. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for designing and building a dashboard. The content is organized as a collection of reference tables and lists rather than a step-by-step process. For a multi-faceted task like dashboard design, there should be a clear sequence (gather requirements → select KPIs → design layout → implement → validate) with checkpoints. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, which provides some structure. However, it's a monolithic file with no references to supporting materials, and several sections (like the full KPI table and chart selection guide) could be split into reference files to keep the main skill lean. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
5e92b71
- Reviewed
Table of Contents
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.