/kpi-dashboard-design
Design and build dashboards that track key performance indicators. Select relevant metrics, visualize data effectively, and communicate insights to stakeholders.
$ npx -y skills add aj-geddes/useful-ai-prompts --skill kpi-dashboard-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/kpi-dashboard-design
Context preview
The summary Claude sees to decide when to auto-load this skill.
Design and build dashboards that track key performance indicators. Select relevant metrics, visualize data effectively, and communicate insights to stakeholders.
SKILL.md
kpi-dashboard-design.SKILL.mdname: kpi-dashboard-design
description: >
Design and build dashboards that track key performance indicators. Select
relevant metrics, visualize data effectively, and communicate insights to
stakeholders.
KPI Dashboard Design
Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
Overview
Effective KPI dashboards make performance visible, enable data-driven decisions, and help teams align around shared goals.
When to Use
- Creating performance measurement systems
- Leadership reporting and visibility
- Operational monitoring
- Project progress tracking
- Team performance management
- Customer health monitoring
- Financial reporting
Quick Start
Minimal working example:
# Select relevant, measurable KPIs
class KPISelection:
KPI_CRITERIA = {
'Relevant': 'Directly aligned with business strategy',
'Measurable': 'Can be quantified and tracked',
'Actionable': 'Team can influence the metric',
'Timely': 'Measured frequently (daily/weekly)',
'Bounded': 'Has clear target/threshold',
'Simple': 'Easy to understand'
}
def identify_business_goals(self):
"""Map goals to KPIs"""
return {
'Revenue Growth': [
'Monthly Recurring Revenue (MRR)',
'Annual Recurring Revenue (ARR)',
'Customer Lifetime Value (CLV)',
'Average Revenue Per User (ARPU)'
],
'Customer Acquisition': [
'Customer Acquisition Cost (CAC)',
'Conversion Rate',
'Traffic to Lead Rate',
// ... (see reference guides for full implementation)Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents | |---|---| | [KPI Selection Framework](references/kpi-selection-framework.md) | KPI Selection Framework | | [Dashboard Design](references/dashboard-design.md) | Dashboard Design | | [Dashboard Implementation](references/dashboard-implementation.md) | Dashboard Implementation | | [KPI Monitoring & Governance](references/kpi-monitoring-governance.md) | KPI Monitoring & Governance |
Best Practices
✅ DO
- Start with business goals, not data
- Limit dashboards to 5-7 core metrics
- Include both leading and lagging indicators
- Assign clear metric ownership
- Update dashboards regularly
- Make drill-down available
- Use visual hierarchy effectively
- Test with actual users
- Include context and benchmarks
- Document metric definitions
❌ DON'T
- Create dashboards without clear purpose
- Include too many metrics (analysis paralysis)
- Forget about data quality
- Build without stakeholder input
- Use confusing visualizations
- Leave dashboards stale
- Ignore mobile viewing experience
- Skip training on dashboard usage
- Create metrics no one can influence
- Change metrics frequently
Read more
name: kpi-dashboard-design description: > Design and build dashboards that track key performance indicators. Select relevant metrics, visualize data effectively, and communicate insights to stakeholders.
KPI Dashboard Design
Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
Overview
Effective KPI dashboards make performance visible, enable data-driven decisions, and help teams align around shared goals.
When to Use
- Creating performance measurement systems
- Leadership reporting and visibility
- Operational monitoring
- Project progress tracking
- Team performance management
- Customer health monitoring
- Financial reporting
Quick Start
Minimal working example:
# Select relevant, measurable KPIs
class KPISelection:
KPI_CRITERIA = {
'Relevant': 'Directly aligned with business strategy',
'Measurable': 'Can be quantified and tracked',
'Actionable': 'Team can influence the metric',
'Timely': 'Measured frequently (daily/weekly)',
'Bounded': 'Has clear target/threshold',
'Simple': 'Easy to understand'
}
def identify_business_goals(self):
"""Map goals to KPIs"""
return {
'Revenue Growth': [
'Monthly Recurring Revenue (MRR)',
'Annual Recurring Revenue (ARR)',
'Customer Lifetime Value (CLV)',
'Average Revenue Per User (ARPU)'
],
'Customer Acquisition': [
'Customer Acquisition Cost (CAC)',
'Conversion Rate',
'Traffic to Lead Rate',
// ... (see reference guides for full implementation)Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents | |---|---| | [KPI Selection Framework](references/kpi-selection-framework.md) | KPI Selection Framework | | [Dashboard Design](references/dashboard-design.md) | Dashboard Design | | [Dashboard Implementation](references/dashboard-implementation.md) | Dashboard Implementation | | [KPI Monitoring & Governance](references/kpi-monitoring-governance.md) | KPI Monitoring & Governance |
Best Practices
✅ DO
- Start with business goals, not data
- Limit dashboards to 5-7 core metrics
- Include both leading and lagging indicators
- Assign clear metric ownership
- Update dashboards regularly
- Make drill-down available
- Use visual hierarchy effectively
- Test with actual users
- Include context and benchmarks
- Document metric definitions
❌ DON'T
- Create dashboards without clear purpose
- Include too many metrics (analysis paralysis)
- Forget about data quality
- Build without stakeholder input
- Use confusing visualizations
- Leave dashboards stale
- Ignore mobile viewing experience
- Skip training on dashboard usage
- Create metrics no one can influence
- Change metrics frequently
488 production-ready AI prompts, all following a standardized template with validated quality gates. Transform ChatGPT, Claude, and other AI assistants into expert consultants.
Repo: aj-geddes/useful-ai-prompts
Other skills on useful-ai-prompts.
- /ab-test-analysis
Design and analyze A/B tests, calculate statistical significance, and determine sample sizes for conversion optimization and experiment validation
Open skill - /access-control-rbac
Implement Role-Based Access Control (RBAC), permissions management, and authorization policies. Use when building secure access control systems with fine-grained permissions.
Open skill - /accessibility-compliance
Implement WCAG 2.1/2.2 accessibility standards, screen reader compatibility, keyboard navigation, and a11y testing. Use when building inclusive web applications, ensuring regulatory compliance, or improving user experience for people with disabilities.
Open skill - /accessibility-testing
Test web applications for WCAG compliance and ensure usability for users with disabilities. Use for accessibility test, a11y, axe, ARIA, keyboard navigation, screen reader compatibility, and WCAG validation.
Open skill - /agile-sprint-planning
Plan and execute effective sprints using Agile methodologies. Define sprint goals, estimate user stories, manage sprint backlog, and facilitate daily standups to maximize team productivity and deliver value incrementally.
Open skill - /alert-management
Implement comprehensive alert management with PagerDuty, escalation policies, and incident coordination. Use when setting up alerting systems, managing on-call schedules, or coordinating incident response.
Open skill

