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.

1.16x

Quality

65%

Does it follow best practices?

Impact

97%

1.16x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/business-analytics/skills/kpi-dashboard-design/SKILL.md

The canonical home for this skill is kpi-dashboard-design in wshobson/agents

Quality

Content

46%Weight 40%Scale 1-5

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

The content is rich and technically sound with concrete code, but it overloads SKILL.md with verbose catalogs, ASCII mockups, and full implementations that should be split into reference files, and it lacks a clear sequenced design workflow with validation checkpoints.

Suggestions

Move the per-department KPI catalogs and full SQL/Streamlit implementations into separate reference files (e.g., references/kpi-catalog.md, references/sql-examples.md) and link to them from SKILL.md to improve progressive disclosure.

Add an explicit step-by-step dashboard design workflow (define audience -> select KPIs -> choose layout pattern -> validate against 5-7 KPI limit and drilldown needs) with checkpoints, rather than presenting topics as standalone sections.

Trim the ASCII dashboard mockups or move them to an assets/reference file; keep SKILL.md as a concise overview pointing to detailed layouts and code.

Dimension	Reasoning	Score
Conciseness	The 428-line body is noticeably verbose: large ASCII dashboard mockups, full per-department KPI catalogs, and lengthy SQL/Streamlit blocks pad the file with reference material that a context window would be better served by keeping leaner.	2 / 5
Actionability	It provides executable SQL and a complete Streamlit example with concrete code, but the bulk of the body is descriptive catalogs and layout sketches rather than uniformly actionable guidance, leaving minor gaps.	4 / 5
Workflow Clarity	There is structure (When to Use, Core Concepts, Layout Patterns, Implementation) but no sequenced design workflow with validation checkpoints; a dashboard-design task has no explicit step-by-step or feedback loop, so the sequence is implicit at best.	3 / 5
Progressive Disclosure	The skill is monolithic: large KPI catalogs, three full ASCII layouts, and full code blocks are all inlined in SKILL.md with no bundle files and no signaling to split detailed material into separate reference files.	2 / 5
	Total	11 / 20 Passed

Description

85%Weight 40%Scale 1-5

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

The description is clear, specific, and well-structured with explicit what-and-when guidance, strong trigger terms, and a distinct niche. Minor tightening of action verbs and addition of synonyms would push specificity and trigger terms to full marks.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ('metrics selection, visualization best practices, and real-time monitoring patterns') and names the domain clearly, but the actions are framed as topics rather than fully concrete verbs, leaving minor coverage gaps.	4 / 5
Completeness	It explicitly 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).	5 / 5
Trigger Term Quality	It includes natural phrases users would say ('building business dashboards', 'selecting metrics', 'designing data visualization layouts') with good coverage, though it omits common synonyms or file/format terms.	4 / 5
Distinctiveness Conflict Risk	The KPI/dashboard niche is specific with distinct triggers and minimal overlap risk with unrelated skills, since the trigger phrases are tightly bound to dashboard/metrics design.	5 / 5
	Total	18 / 20 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: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/business-analytics/skills/kpi-dashboard-design/SKILL.md
Commit: 6453c0b

Reviewed: about 10 hours 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.