Skip to content
SkillModel-led1,202 tokens in use

metrics-dashboard

Design a product metrics dashboard with a North Star, input and health metrics, layout, review cadence and alert rules.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-product-discovery/skills/metrics-dashboard
claude plugin install pm-product-discovery@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing metrics-dashboard costs

48tokens idle
1,202tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples6/15
  • Output10/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

This skill designs a product metrics dashboard in layers: a North Star Metric, three to five input metrics, health guardrails and business metrics. Each metric gets an exact definition, a data source, a visualization, a target and an alert threshold.

It draws on the Lean Analytics criteria for a good metric (understandable, comparative, a ratio or rate, behavior-changing) and separates vanity from actionable and leading from lagging metrics. The output is a dashboard specification in markdown.

What You Get

  • A layered metric set: North Star, input metrics, health metrics and business metrics
  • A table with definition, data source, chart type, target and alert threshold per metric
  • A dashboard layout sketch
  • A review cadence and alert plan with owners and response times

Common Use Cases

  • Setting up product analytics for a new launch
  • Auditing an existing dashboard for vanity metrics
  • Turning OKRs into a set of tracked metrics with alerts

What Makes It Unique

It embeds a short metrics theory (four criteria for a good metric, eight metric types, five action steps) so the dashboard is checked against whether each number would change behavior. It also fixes a review cadence and alert ownership, which many dashboard templates leave out.

Under The Hood

The skill is a prompt only, with no scripts. It tells the agent to read any dashboards, analytics exports, OKRs or strategy files the user supplies, and to save the specification as a markdown document. It names analytics and dashboard tools as suggestions but does not call any of them or any web service.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers