kpi-dashboard-design

Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use this skill when building an executive SaaS metrics dashboard tracking MRR, churn, and LTV/CAC ratios; designing an operations center with live service health and request throughput; creating a cohort retention analysis view for a product team; or debugging a dashboard where metrics contradict each other due to inconsistent calculation methodology.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured body with strong executable examples and clean progressive disclosure to a real reference file. Its main weaknesses are restating well-known concepts (SMART KPIs) and omitting validation checkpoints in the database-related troubleshooting fixes.

Suggestions

Drop or compress the SMART KPIs definitions and the 'Comprehensive patterns for...' opener — Claude already knows these — and keep only the non-obvious KPI framework/hierarchy structure.

Add an explicit validation checkpoint to the database troubleshooting fixes (e.g., after running the cohort fix, verify cohort sizes with a quick COUNT query before trusting the trend; after refresh_mrr_summary, confirm the snapshot row updated).

For the 'metrics contradict each other' and alert-fatigue entries, add a short verify step so the fix→confirm loop is explicit rather than implied.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the SMART KPIs block ('Specific: Clear definition', 'Measurable: Quantifiable') and the 'Comprehensive patterns for designing...' opener restate basic business concepts Claude already knows, so it is not fully lean.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code — the MRR normalization CASE statement, the cohort DATE_TRUNC fix, the refresh_mrr_summary job, and the is_anomalous detector — alongside concrete do/don't guidance.	3 / 3
Workflow Clarity	Troubleshooting entries give a clear problem→cause→fix sequence, but the database-related fixes (summary-table refresh, cohort SQL) lack explicit validate-then-proceed checkpoints, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	SKILL.md is a concise overview that points one level deep to the real, verified references/details.md for detailed KPI lists and layout patterns, with a clearly signaled navigation cue ('Read that file when the navigation summary above is insufficient').	3 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete capabilities, and an explicit 'Use this skill when' clause with multiple realistic trigger scenarios. It clearly communicates both what the skill does and when to invoke it with minimal fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'metrics selection, visualization best practices, and real-time monitoring patterns' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns') and when ('Use this skill when building...'), with an explicit 'Use this skill when' trigger clause.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'executive SaaS metrics dashboard tracking MRR, churn, and LTV/CAC ratios', 'operations center with live service health and request throughput', 'cohort retention analysis' — giving good coverage of natural phrasings.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear KPI-dashboard-design niche with distinct, specific triggers (LTV/CAC ratios, cohort retention, metrics contradicting each other), making it unlikely to fire for an unrelated skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Commit: 5cc2549

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.