kpi-dashboard-design
Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use when building business dashboards, selecting metrics, or designing data visualization layouts.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill kpi-dashboard-designOverall
score
78%
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/skillEvaluation — 97%
↑ 1.09xAgent success when using this skill
Validation 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 well-crafted skill description that clearly articulates specific capabilities and includes explicit 'Use when' guidance with natural trigger terms. The description uses proper third-person voice and covers the dashboard design domain comprehensively. Minor weakness is potential overlap with general data visualization skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'metrics selection', 'visualization best practices', and 'real-time monitoring patterns'. These are distinct, actionable capabilities within the KPI dashboard domain. | 3 / 3 |
Completeness | Clearly answers both what ('Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns') and when ('Use when building business dashboards, selecting metrics, or designing data visualization layouts') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'KPI dashboards', 'business dashboards', 'metrics', 'data visualization', 'layouts'. These cover common variations of how users would describe dashboard-related tasks. | 3 / 3 |
Distinctiveness Conflict Risk | While 'KPI dashboards' is fairly specific, 'data visualization' could overlap with general charting or visualization skills. The focus on dashboards and metrics helps, but 'visualization best practices' is broad enough to potentially conflict with other design-focused skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable content with executable SQL and Python code examples, plus well-designed ASCII dashboard mockups. However, it's verbose with content that could be condensed (SMART criteria, extensive KPI lists) and lacks a clear step-by-step workflow for actually designing a dashboard. The monolithic structure would benefit from splitting detailed reference material into separate files.
Suggestions
Add a clear step-by-step workflow section (e.g., '1. Identify audience → 2. Select 5-7 KPIs → 3. Choose layout pattern → 4. Implement → 5. Validate with stakeholders') with explicit checkpoints
Move the extensive KPI lists by department to a separate KPIS_REFERENCE.md file and link to it
Remove the SMART criteria explanation - Claude knows this framework already
Split the implementation code examples into a separate IMPLEMENTATION.md file, keeping only a brief example in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some content Claude already knows (SMART criteria explanation, basic concepts). The extensive KPI lists by department and multiple dashboard patterns add bulk that could be condensed or moved to reference files. | 2 / 3 |
Actionability | Provides fully executable SQL queries for KPI calculations and complete Python/Streamlit code for dashboard implementation. The code examples are copy-paste ready with realistic data and proper imports. | 3 / 3 |
Workflow Clarity | While the content is well-organized with clear sections, there's no explicit workflow for designing a dashboard (no step-by-step process with validation checkpoints). The 'When to Use' section lists scenarios but doesn't guide through the actual design process. | 2 / 3 |
Progressive Disclosure | Content is structured with headers but is monolithic - the extensive KPI lists, multiple dashboard patterns, and full code examples could be split into separate reference files. External resources are listed but internal content organization could benefit from splitting. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.