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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill kpi-dashboard-design78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 skill description that clearly articulates specific capabilities and includes an explicit 'Use when' clause with relevant trigger terms. The description effectively communicates the skill's purpose using concrete actions and natural language. Minor weakness is potential overlap with other data visualization or analytics skills.
| 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' and 'executive dashboards' are fairly specific, there could be overlap with general data visualization skills or business analytics skills. The term 'analytics views' is somewhat broad. | 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 diagrams. 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 implementation steps limits its practical utility.
Suggestions
Add a step-by-step workflow for designing a dashboard (e.g., 1. Identify stakeholder goals, 2. Select 5-7 KPIs, 3. Choose visualizations, 4. Design layout, 5. Validate with stakeholders)
Include executable code examples for at least one framework (React/Chart.js, Python/Plotly, or similar) showing how to implement the described layout
Add a validation checkpoint such as 'Review checklist before presenting: Does each KPI have an owner? Is comparison period shown? Are colors consistent?'
| 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 of KPIs, chart types) without a step-by-step workflow or validation checkpoints. | 1 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is inline in one file. For a skill of this scope, some content (like detailed chart selection guidance or implementation examples) could be split into referenced files. | 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.
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.