CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

metrics-dashboard

Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pm-product-discovery/skills/metrics-dashboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 body delivers a well-structured, actionable design workflow with concrete templates and tool recommendations. Its main weaknesses are an explanation-heavy Domain Context section that pads token usage and the lack of explicit validation checkpoints integrated into the step sequence.

Suggestions

Trim the Domain Context section to the essentials Claude does not already know (e.g., keep the NSM/Input/Health layering) and move the Lean Analytics criteria, 8 metric types, and 5 action steps into a reference file linked from the body.

Integrate an explicit validation checkpoint into the Instructions, e.g. a step after defining metrics: "Audit each metric against the 4 good-metric criteria and drop or replace any that fail".

Show one worked example of a completed metric row (filled-in table entry with real numerator/denominator, data source, and alert threshold) so the template becomes fully concrete.

DimensionReasoningScore

Conciseness

The Domain Context section spends ~20 lines explaining concepts Claude largely already knows (Lean Analytics criteria, "8 metric types", "5 action steps"), and eight Further Reading links add bulk; the body is mostly efficient but noticeably could be tightened.

3 / 5

Actionability

Concrete guidance throughout — a metric table with exact columns (numerator/denominator, time window, alert threshold), an ASCII dashboard layout mockup, specific review cadences, and named tools (Amplitude, Mixpanel, PostHog, Looker, Metabase, Datadog, Grafana). Minor gap: the table template is never shown filled in with a worked example.

4 / 5

Workflow Clarity

The six numbered steps form a clear sequence, but validation checkpoints are only implicit — the "audit metrics against the 4 good-metric criteria" action lives in Domain Context rather than being an explicit step in the workflow.

3 / 5

Progressive Disclosure

Well-organized single-file skill with clearly labeled Further Reading links (one level deep, external). At ~90 lines with inlined educational Domain Context that could live in a reference file, it stops short of the anchor-5 clean split.

4 / 5

Total

14

/

20

Passed

Description

83%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.

A strong description that clearly states both capabilities and explicit trigger conditions in third person, with concrete component coverage. Its only weaknesses are limited verb variety and a few missing natural synonyms (e.g., "KPI dashboard", "OKRs").

DimensionReasoningScore

Specificity

"Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds" covers the domain's components comprehensively, but relies on only two action verbs (define, design) rather than the multiple distinct concrete actions of the anchor-5 example.

4 / 5

Completeness

Explicitly answers both what ("Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds") and when ("Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan" includes natural phrases users would say, but misses common variations and synonyms such as "KPI dashboard", "product metrics", "OKRs", or "North Star Metric".

4 / 5

Distinctiveness Conflict Risk

The product-metrics-dashboard niche with KPI/analytics triggers is mostly distinct, with only minor overlap risk against generic dashboard, dataviz, or business-analytics skills.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-product-discovery/skills/metrics-dashboard/SKILL.md

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.