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 well-crafted skill description that clearly communicates both what the skill does and when to use it, with strong natural trigger terms. The explicit 'Use when' clause with multiple trigger scenarios is effective. The only minor weakness is potential overlap with adjacent skills in data visualization or analytics domains.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'metric selection', 'visual hierarchy', and 'data visualization best practices', along with specific outputs like 'KPI dashboards', 'executive dashboards', 'analytics views'. | 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') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'KPI', 'dashboard', 'executive dashboards', 'analytics views', 'business metrics', 'data visualization'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | While 'KPI dashboards' is fairly specific, there could be overlap with general data visualization skills, charting skills, or broader UI/UX design skills. The term 'analytics views' is somewhat broad and could conflict with data analysis or reporting skills. | 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 reference guide for KPI dashboard design rather than actionable instructions Claude can execute. It has decent structure and some useful concrete elements (ASCII layout, CSS snippet, chart selection table), but lacks executable code for actually building dashboards with specific frameworks, has no workflow sequencing, and includes generic business knowledge Claude already possesses.
Suggestions
Add a clear step-by-step workflow for dashboard creation (e.g., 1. Gather requirements → 2. Select KPIs → 3. Design layout → 4. Implement with [framework] → 5. Review with stakeholder) with validation checkpoints at each stage.
Replace or supplement the CSS snippet with complete, executable dashboard component examples using a specific framework (e.g., React + Recharts, or a Python Dash example) that Claude can adapt.
Remove generic KPI selection advice and common business KPI lists that Claude already knows; focus instead on project-specific decision trees or templates Claude can fill in.
Add references to separate files for detailed topics like chart library API patterns or framework-specific implementation guides to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with good use of tables and lists, but includes some content Claude already knows (e.g., 'Good KPIs are: Relevant to business goals, Measurable and quantifiable' is textbook-level knowledge). The 'Common Mistakes' and 'Best Practices' sections contain generic advice that doesn't add much beyond what Claude would already know. | 2 / 3 |
Actionability | Provides some concrete guidance like the CSS snippet and ASCII layout diagram, but overall reads more like a reference/checklist than executable instructions. There's no complete, copy-paste-ready dashboard implementation—no actual charting library code (e.g., Chart.js, D3, Recharts), no data fetching patterns, and no working component examples. | 2 / 3 |
Workflow Clarity | There is no sequenced workflow for 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-step design task like dashboard creation, there should be a clear sequence (e.g., 1. Select KPIs → 2. Design layout → 3. Implement charts → 4. Validate with stakeholders) with checkpoints. | 1 / 3 |
Progressive Disclosure | Content is organized into clear sections with headers, which aids scanning. However, everything is inline in a single file with no references to deeper materials. The chart selection guide and CSS examples could be split into separate reference files, and the skill would benefit from linking to framework-specific implementation guides. | 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
88da5ff
- 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.