Kpi Dashboard Design
- 392 installs
- 202 repo stars
- Updated August 4, 2026
- secondsky/claude-skills
kpi-dashboard-design is a Claude agent skill that designs effective KPI dashboards with metric selection, visual hierarchy, and data visualization best practices for developers building executive dashboards and analytics
About
kpi-dashboard-design is an MIT-licensed agent skill from secondsky/claude-skills that guides Claude to design KPI dashboards with sound metric selection, visual hierarchy, and data visualization best practices. Developers use it when building executive dashboards, analytics views, or business metric presentations that must communicate MRR, CAC, conversion, and retention clearly. The skill includes a KPI selection framework requiring metrics to be relevant, measurable, team-influenced, frequently updated, and simple to understand. Reach for it before coding dashboard UI when metric choices and layout hierarchy need structure.
- kpi-dashboard-design
Kpi Dashboard Design by the numbers
- 392 all-time installs (skills.sh)
- +14 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #1,066 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/secondsky/claude-skills --skill kpi-dashboard-designAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 392 |
|---|---|
| repo stars | ★ 202 |
| Last updated | August 4, 2026 |
| Repository | secondsky/claude-skills ↗ |
How do you design an effective KPI dashboard?
Use kpi-dashboard-design for development tasks
Who is it for?
Developers or analytics engineers designing executive dashboards who need structured KPI selection and visualization hierarchy before implementation.
Skip if: Teams needing ETL pipeline design, warehouse modeling, or backend metric computation without dashboard UI planning.
When should I use this skill?
A task asks to design executive dashboards, select business KPIs, or plan analytics view layout and visual hierarchy.
What you get
KPI selection frameworks, dashboard layout specs, visual hierarchy plans, and metric visualization guidelines.
- KPI selection framework
- Dashboard layout specs
- Visualization guidelines
By the numbers
- KPI framework uses 5 selection criteria: relevant, measurable, team-influenced, frequent, simple
- Reference table covers 4 business goal areas: revenue, acquisition, retention, and related KPIs
Files
KPI Dashboard Design
Design effective dashboards that communicate key metrics clearly.
KPI Selection Framework
Good KPIs are:
- Relevant to business goals
- Measurable and quantifiable
- Influenced by the team
- Updated frequently
- Simple to understand
Common Business KPIs
| Goal | KPIs |
|---|---|
| Revenue | MRR, ARR, Revenue Growth |
| Acquisition | CAC, New Users, Conversion Rate |
| Retention | Churn Rate, NPS, DAU/MAU |
| Efficiency | LTV:CAC, Burn Rate |
| Quality | Error Rate, Response Time |
Dashboard Layout
┌─────────────────────────────────────────────────┐
│ Executive Summary │
│ [Revenue ▲12%] [Users ▲8%] [Churn ▼2%] │
├─────────────────────┬───────────────────────────┤
│ │ │
│ Revenue Trend │ User Acquisition │
│ (Line Chart) │ (Bar Chart) │
│ │ │
├─────────────────────┼───────────────────────────┤
│ │ │
│ Retention Funnel │ Top Products │
│ (Funnel Chart) │ (Table) │
│ │ │
└─────────────────────┴───────────────────────────┘Visual Design Principles
/* Traffic light colors for status */
.metric-good { color: #22c55e; } /* Green */
.metric-warning { color: #f59e0b; } /* Amber */
.metric-bad { color: #ef4444; } /* Red */
/* Visual hierarchy */
.metric-primary {
font-size: 2.5rem;
font-weight: 700;
}
.metric-secondary {
font-size: 1.5rem;
font-weight: 500;
}Chart Selection
| Data Type | Chart |
|---|---|
| Trend over time | Line chart |
| Comparison | Bar chart |
| Composition | Pie/Donut |
| Distribution | Histogram |
| Correlation | Scatter plot |
| Funnel stages | Funnel chart |
Interactivity Features
- Drill-down to detailed views
- Date range selection
- Filtering by segment
- Export to CSV/PDF
- Scheduled email reports
Best Practices
- Limit to 5-7 KPIs per dashboard
- Show trends, not just snapshots
- Use consistent color coding
- Include comparison periods (vs last month)
- Update data in real-time or hourly
- Review dashboard relevance quarterly
Common Mistakes
- Too many metrics (information overload)
- No clear visual hierarchy
- Missing context (no comparisons)
- Outdated or stale data
- Metrics without ownership
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kFAQ
What makes a good KPI in kpi-dashboard-design?
kpi-dashboard-design defines good KPIs as relevant to business goals, measurable, influenced by the team, updated frequently, and simple to understand before mapping them to dashboard layouts.
Does kpi-dashboard-design write ETL code?
kpi-dashboard-design focuses on metric selection, visual hierarchy, and dashboard design for executive analytics views. It does not target ETL pipelines or warehouse modeling.