
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.
- Installs
- 3K
- Last 24h
- +8
- Trending rank
- #9387
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/phuryn/pm-skills --skill metrics-dashboard- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads metrics-dashboard automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
-
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
-
For each metric, define:
Metric Definition Data Source Visualization Target Alert 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] -
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] │ └─────────────────────────────────────────────┘ -
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
-
Define alerts:
- What thresholds trigger investigation?
- Who gets alerted and through what channel?
- What's the expected response time?
-
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
- The Ultimate List of Product Metrics
- The North Star Framework 101
- The Product Analytics Playbook: AARRR, HEART, Cohorts & Funnels for PMs
- AARRR (Pirate) Metrics: The 5-Stage Framework for Growth
- The Google HEART Framework: Your Guide to Measuring User-Centric Success
- Funnel Analysis 101: How to Track and Optimize Your User Journey
- Are You Tracking the Right Metrics?
- Continuous Product Discovery Masterclass (CPDM) (video course)
FAQ
What does the metrics-dashboard skill do?
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.
How do I install metrics-dashboard?
Run npx skills add https://github.com/phuryn/pm-skills --skill metrics-dashboard in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/metrics-dashboard/ (personal) or .claude/skills/metrics-dashboard/ (project).
Which AI agents can use metrics-dashboard?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is metrics-dashboard safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains metrics-dashboard?
It is published by phuryn in phuryn/pm-skills. It has 3,008 recorded installs.
More from phuryn/pm-skills
create-prd
phuryn/pm-skills
Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
pre-mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
prioritization-frameworks
phuryn/pm-skills
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
outcome-roadmap
phuryn/pm-skills
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
strategy-red-team
phuryn/pm-skills
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
competitor-analysis
phuryn/pm-skills
Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.