phuryn/metrics-dashboard
pm-product-discovery/skills/metrics-dashboard/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills metrics-dashboardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 2:44 PM96.4s1 file scanned
SKILL.md
- name:
- metrics-dashboard
- description:
- 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.
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)
Related Skills
phuryn/strategy-red-team
testing
VerifiedTrustedCommunity
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.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/shipping-artifacts
tools
VerifiedTrustedCommunity
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/intended-vs-implemented
development
VerifiedTrustedCommunity
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/review-resume
testing
VerifiedTrustedCommunity
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
7,806SKILL.mdUpdated Mar 20, 2026