phuryn/pm-skills

metrics-dashboard

Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/phuryn/pm-skills --skill metrics-dashboard

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

  1. 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]
  1. 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]        │
   └─────────────────────────────────────────────┘
  1. 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
  1. Define alerts:
  • What thresholds trigger investigation?
  • Who gets alerted and through what channel?
  • What's the expected response time?
  1. 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

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
phuryn
커뮤니티

strategy-red-team

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.

1시간 설치 수
4
GitHub Stars
2.8만
업데이트
11월 8일
phuryn
커뮤니티

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

1시간 설치 수
2
GitHub Stars
2.8만
업데이트
11월 8일
phuryn
커뮤니티

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

1시간 설치 수
2
GitHub Stars
2.8만
업데이트
11월 8일
phuryn
커뮤니티

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1시간 설치 수
2
GitHub Stars
2.8만
업데이트
11월 8일