New to Claude Skills? Learn how to install them →

phuryn on GitHub

Product Metrics Dashboard

Free

Design a comprehensive product metrics dashboard.

by phuryn25.1k stars on phuryn/pm-skills
1 views
Updated Jul 3, 2026
Get this skill

Free · Opens the source repo

What Product Metrics Dashboard does

The Product Metrics Dashboard skill provides a structured approach to designing and defining a metrics dashboard tailored to your product's needs. It guides users through the process of selecting key metrics, determining appropriate data sources, choosing visualization types, and setting alert thresholds. This skill is particularly useful for product managers, analysts, and teams involved in product analytics or performance monitoring.

The skill emphasizes the importance of distinguishing between metrics, KPIs, and North Star Metrics, ensuring that users understand how to select and prioritize the right data points. It also introduces criteria for good metrics, helping users avoid common pitfalls associated with vanity metrics and ensuring that the metrics chosen will drive actionable insights. By following the outlined steps, users can create a dashboard that not only tracks performance but also influences decision-making processes.

Additionally, the skill provides a framework for organizing metrics into layers, such as North Star Metrics and health metrics, which helps in maintaining a clear focus on product performance. It encourages a systematic approach to dashboard design, including layout suggestions and review cadences to keep the metrics relevant and actionable. Users can also define alert thresholds to proactively manage product health and respond to changes in performance.

Overall, this skill is a valuable resource for anyone looking to establish a robust metrics dashboard that aligns with their product strategy and goals, ensuring that they are tracking the right metrics to drive success.

When to use it

Use this skill when you need to create or refine a product metrics dashboard that effectively tracks performance and informs decision-making.

When not to use it

This skill may not be suitable for users looking for a fully automated dashboard solution, as it focuses on guiding the design process rather than providing a ready-made tool.

What you can build with it

Creating a New Dashboard

When starting from scratch, this skill helps you identify the right metrics and layout for your product metrics dashboard.

Refining Existing Dashboards

If you have existing dashboards, use this skill to audit and improve the metrics being tracked, ensuring they align with your goals.

Setting Up Alerts

Define alert thresholds for key metrics to proactively monitor product health and respond to issues as they arise.

How to install Product Metrics Dashboard

View source

1. Install with the skills CLI

npx skills add phuryn/pm-skills/metrics-dashboard --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by phuryn

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

Frequently asked questions about Product Metrics Dashboard

Similar skills