pm-metrics-tracking

Define metrics hierarchies, OKR targets, and dashboard designs for product tracking.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kirillshilin/instructions --skill pm-metrics-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-metrics-tracking
Source: https://github.com/kirillshilin/instructions/tree/main/obsolete/dotgithub/skills/pm-metrics-tracking
Command: npx skills add https://github.com/kirillshilin/instructions --skill pm-metrics-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams struggle to consistently define, track, and analyse core metrics across goals, OKRs, and dashboards, leading to misaligned priorities and delayed decision making.

Core Features & Use Cases

  • Define a metrics hierarchy (North Star, 1–2 L1 indicators per lifecycle stage, and diagnostic L2 metrics) to align teams on outcomes.
  • Set OKR targets and run regular reviews to measure progress and drive strategy.
  • Design dashboards and alerting to surface current values, comparisons, trends, and anomalies for timely action.
  • Use Case: A product area wants to monitor activation, engagement, retention, monetization, and satisfaction, and link these metrics to quarterly OKRs.

Quick Start

Create a simple, end-to-end metrics setup that captures North Star, L1, and L2 indicators and presents them in a dashboard.

Frequently Asked Questions about pm-metrics-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a product metrics hierarchy with OKRs?

A product metrics scorecard tracks current values, comparisons, and trends for your core indicators against quarterly OKR targets. It surfaces anomalies and engagement metrics to drive timely strategy adjustments during regular review cadences.

What is the best way to track product metrics across lifecycle stages?

Dashboard design for OKR tracking should surface current metric values, comparisons, and trends for your L1 and L2 indicators. Include alerting to highlight anomalies, ensuring timely action and alignment with your quarterly OKR targets during review cadences.

Can I use this approach for quarterly OKR planning and progress reviews?

Trend analysis for product management identifies anomalies and tracks L1 indicators like retention and monetization over time. Linking these trends to your OKR targets during regular reviews surfaces insights for timely strategic action.

How do I design dashboards and alerting for product metric anomalies?

Dashboards for product metrics should display current values, comparisons, and trend lines for your North Star and L1 indicators. Apply an actionable alerting design to flag anomalies, supporting timely decisions during regular OKR review cadences.

Do I need a defined metrics hierarchy before tracking OKRs?

You should avoid dashboard designs that lack alerting or fail to surface anomalies in your L1 and L2 metrics. Without linking trends to OKR targets and maintaining a regular review cadence, delayed decision making and misaligned priorities persist.