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.
80
72%
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 articulates both capabilities and usage triggers. It uses appropriate third-person voice and includes natural trigger terms. The only minor weakness is potential overlap with general data visualization or analytics skills, though the KPI/dashboard focus provides reasonable distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'proper metric selection', 'visual hierarchy', and 'data visualization best practices'. Uses third person voice ('Designs') appropriately. | 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 natural keywords users would say: 'KPI dashboards', 'executive dashboards', 'analytics views', 'business metrics'. These are terms users naturally use when requesting this type of work. | 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 analysis skills. The focus on dashboards helps but isn't fully distinct. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid reference guide for KPI dashboard design with efficient use of tables and visual examples. However, it reads more like a cheat sheet than actionable guidance—it tells Claude what good dashboards contain but not how to systematically design one. The lack of a clear workflow or step-by-step process limits its utility for actually building dashboards.
Suggestions
Add a step-by-step workflow section (e.g., '1. Identify stakeholder goals → 2. Select 5-7 KPIs → 3. Choose layout → 4. Validate with stakeholders') with explicit checkpoints
Include executable code examples for at least one dashboard framework (e.g., React with Recharts, or a Python Dash example) rather than just CSS snippets
Add a concrete example showing the full process: given business context X, here are the selected KPIs, layout decisions, and resulting dashboard structure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and visual diagrams instead of verbose explanations. It assumes Claude understands dashboard concepts and doesn't over-explain basic ideas. | 3 / 3 |
Actionability | Provides concrete CSS examples and visual layout diagrams, but lacks executable code for actually building dashboards. The guidance is more descriptive (what to include) than instructive (how to implement). | 2 / 3 |
Workflow Clarity | No clear sequence or process for designing a dashboard. Content is organized as reference material (lists, tables) rather than a workflow with steps. Missing any validation checkpoints for dashboard design. | 1 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but everything is inline in one file. For a skill of this scope, some content (like detailed chart selection guidance or CSS patterns) could be referenced externally. | 2 / 3 |
Total | 8 / 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.
90d6bd7
Table of Contents
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.