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.
65
48%
Does it follow best practices?
Impact
97%
1.16xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/business-analytics/skills/kpi-dashboard-design/SKILL.mdQuality
Discovery
82%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 solid description that follows good structural patterns with an explicit 'Use when' clause and uses third-person voice correctly. Its main weaknesses are that the capability descriptions lean toward abstract concepts ('best practices', 'patterns') rather than concrete actions, and some trigger terms like 'data visualization' could cause overlap with other skills. The KPI/dashboard focus provides reasonable distinctiveness but could be sharper.
Suggestions
Replace abstract terms like 'best practices' and 'patterns' with concrete actions such as 'create gauge charts, configure alert thresholds, design metric hierarchies'.
Narrow the 'data visualization layouts' trigger to something more specific like 'KPI layouts' or 'dashboard grid layouts' to reduce conflict risk with general visualization skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (KPI dashboards) and some actions (metrics selection, visualization best practices, real-time monitoring patterns), but these are somewhat abstract rather than concrete actions like 'create gauge charts' or 'configure alert thresholds'. Terms like 'best practices' and 'patterns' are vague. | 2 / 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 an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes good natural keywords users would say: 'KPI dashboards', 'business dashboards', 'metrics', 'data visualization', 'real-time monitoring', 'layouts'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | While 'KPI dashboards' is fairly specific, terms like 'data visualization' and 'metrics' could overlap with general data analysis or charting skills. The 'designing data visualization layouts' trigger could conflict with a more general data visualization skill. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a comprehensive reference guide or textbook chapter on KPI dashboards than an actionable skill for Claude. It is extremely verbose, spending most of its token budget on general business knowledge (KPI lists, SMART framework) that Claude already knows. While the SQL and Python code examples are concrete and executable, the skill lacks a clear workflow for actually designing a dashboard and would benefit enormously from being restructured into a concise overview with references to detailed sub-files.
Suggestions
Add a clear step-by-step workflow for dashboard design (e.g., 1. Identify audience and KPI level, 2. Select 5-7 KPIs, 3. Choose layout pattern, 4. Implement with code, 5. Validate with stakeholders) with explicit validation checkpoints.
Remove or drastically reduce the department KPI lists - Claude already knows common business metrics. Instead, provide a brief framework for KPI selection criteria.
Split implementation code (SQL queries, Streamlit app), layout patterns (ASCII mockups), and KPI references into separate files and reference them from a concise overview.
Remove the SMART KPI explanation and other textbook concepts that Claude already understands, focusing instead on project-specific decision guidance (e.g., when to use which layout pattern, how to choose between real-time vs batch updates).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Extensive lists of KPIs by department (Sales, Marketing, Product, Finance) are general business knowledge Claude already knows. The ASCII dashboard mockups, while visually interesting, consume enormous token budget. The SMART KPI framework and department KPI lists are textbook content that adds no novel instruction. | 1 / 3 |
Actionability | The SQL queries and Streamlit Python code are executable and concrete, which is good. However, much of the skill is descriptive lists and ASCII art rather than actionable guidance. The code examples are useful but represent only one implementation path, and there's no guidance on how to adapt them to specific situations or connect them to real data sources. | 2 / 3 |
Workflow Clarity | There is no clear workflow or sequenced process for designing a dashboard. The content is organized as reference material (lists of KPIs, layout patterns, code snippets) but lacks a step-by-step process: no 'first do X, then Y, validate Z' structure. For a skill about 'designing' dashboards, the absence of a design workflow is a significant gap. | 1 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of content with no references to external files. The SQL queries, full Streamlit app code, ASCII dashboard layouts, and exhaustive KPI lists are all inline. Department-specific KPIs, implementation code, and layout patterns should be split into separate referenced files. The Resources section links to external websites rather than companion skill files. | 1 / 3 |
Total | 5 / 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
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- 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.