mcpField
M
metrics-dashboard

metrics-dashboard

github.com/phurynData & databases27.5k3.0k installsUpdated 2w ago
Repository

About metrics-dashboard

A dashboard-design skill for product teams that organizes metrics, visualizations, and alert thresholds around a product context. It also specifies review cadences and recommends tools, then saves the dashboard specification as Markdown.

Key features

  1. 01Organizes North Star, input, health, and business metrics
  2. 02Defines calculations, sources, and targets
  3. 03Plans chart layouts and alert thresholds
  4. 04Sets metric review cadences
  5. 05Recommends analytics and monitoring tools
  6. 06Produces a Markdown dashboard specification

Use cases

  1. 01Designing a metrics framework for a new product
  2. 02Reviewing whether existing metrics drive action
  3. 03Setting alerts for key metrics

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/phuryn/pm-skills --skill metrics-dashboard

After installing, type/metrics-dashboardin Claude Code to confirm it loaded.

Details

From the project README

Product Metrics Dashboard

Design a comprehensive product metrics dashboard with the right metrics, visualizations, and alert thresholds.

Context

You are designing a metrics dashboard for $ARGUMENTS.

If the user provides files (existing dashboards, analytics data, OKRs, or strategy docs), read them first.

Domain Context

Metrics vs KPIs vs NSM: Metrics = all measurable things. KPIs = a few key quantitative metrics tracked over a longer period. North Star Metric = a single customer-centric KPI that is a leading indicator of business success.

4 criteria for a good metric (Ben Yoskovitz, Lean Analytics): (1) Understandable — creates a common language. (2) Comparative — over time, not a snapshot. (3) Ratio or Rate — more revealing than whole numbers. (4) Behavior-changing — the Golden Rule: "If a metric won't change how you behave, it's a bad metric."

8 metric types: Vanity vs Actionable (only actionable metrics change behavior), Qualitative vs Quantitative (WHAT vs WHY — you need both; never stop talking to customers), Exploratory vs Reporting (explore data to uncover unexpected insights), Lagging vs Leading (leading indicators enable faster learning cycles, e.g. customer complaints predict churn).

5 action steps: (1) Audit metrics against the 4 good-metric criteria. (2) Update dashboards — ensure all key metrics are good ones. (3) Identify vanity metrics — be careful how you use them. (4) Classify leading vs lagging indicators. (5) Pick one problem and dig deep into the data.

For case studies and more detail: Are You Tracking the Right Metrics? by Ben Yoskovitz

Instructions
  1. Identify the metrics framework — organize metrics into layers:

    North Star Metric: The single metric that best captures core value delivery

    Input Metrics (3-5): The levers that drive the North Star

    Health Metrics: Guardrails that ensure overall product health

    Business Metrics: Revenue, cost, and unit economics

  2. For each metric, define:

    MetricDefinitionData SourceVisualizationTargetAlert Threshold
    [Name][Exact calculation: numerator/denominator, time window][Where the data comes from][Line chart / Bar / Number / Funnel][Goal value][When to trigger an alert]
  3. Design the dashboard layout:

    ┌─────────────────────────────────────────────┐
    │  NORTH STAR: [Metric] — [Current Value]     │
    │  Trend: [↑/↓ X% vs last period]             │
    ├──────────────────┬──────────────────────────┤
    │  Input Metric 1  │  Input Metric 2          │
    │  [Sparkline]     │  [Sparkline]             │
    ├──────────────────┼──────────────────────────┤
    │  Input Metric 3  │  Input Metric 4          │
    │  [Sparkline]     │  [Sparkline]             │
    ├──────────────────┴──────────────────────────┤
    │  HEALTH: [Latency] [Error Rate] [NPS]       │
    ├─────────────────────────────────────────────┤
    │  BUSINESS: [MRR] [CAC] [LTV] [Churn]        │
    └─────────────────────────────────────────────┘
    
  4. Set review cadence:

    • Daily: Operational health (errors, latency, critical flows)
    • Weekly: Input metrics and engagement trends
    • Monthly: North Star, business metrics, OKR progress
    • Quarterly: Strategic review and metric recalibration
  5. Define alerts:

    • What thresholds trigger investigation?
    • Who gets alerted and through what channel?
    • What's the expected response time?
  6. Recommend tools based on the user's context:

    • Amplitude, Mixpanel, PostHog for product analytics
    • Looker, Metabase, Mode for SQL-based dashboards
    • Datadog, Grafana for operational health

Think step by step. Save the dashboard specification as a markdown document.


Further Reading

Comments

Markdown supported