metrics-tracking

Define product metrics and design dashboards for metric reviews.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SMOrchestra-ai/smorch-brain --skill metrics-tracking-smorchestra-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metrics-tracking
Source: https://github.com/SMOrchestra-ai/smorch-brain/tree/main/plugins/product-management/skills/metrics-tracking
Command: npx skills add https://github.com/SMOrchestra-ai/smorch-brain --skill metrics-tracking-smorchestra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity around which metrics matter and how to track them so product teams can focus on measurable outcomes instead of vanity numbers. It helps teams choose a North Star, build a concise L1 scorecard, diagnose issues with L2 diagnostics, and create dashboards and cadences that lead to action.

Core Features & Use Cases

  • Metric hierarchy & North Star selection: Identify a single north star metric and a 5-7 metric L1 health scorecard mapped across acquisition, activation, engagement, retention, monetization, and satisfaction.
  • Diagnostic tooling & cohort analysis: Provide L2 metrics and funnel checkpoints for troubleshooting retention drops, conversion bottlenecks, and feature adoption gaps.
  • Goal setting & cadence: Templates and best practices for OKRs, weekly checks, monthly reviews, and quarterly business reviews that tie metrics to decisions.
  • Dashboard design: Principles for layout, context, comparisons, visual status indicators, and alert hygiene to ensure dashboards are actionable not noisy.
  • Use case: A PM setting quarterly OKRs can use the Skill to define a north star, pick 3 OKRs with measurable KRs, design a dashboard that shows progress, and set weekly review agenda items.

Quick Start

Ask the metrics-tracking skill to "Help me define a North Star metric and a 7-metric L1 scorecard for a B2B SaaS onboarding product and draft a weekly metrics review agenda."

Frequently Asked Questions about metrics-tracking

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

FAQPage Schema
How do I define a North Star metric and build a product health scorecard?

To define a North Star metric and build a scorecard, identify a single metric representing core product value, then map 5-7 L1 metrics across acquisition, activation, engagement, retention, monetization, and satisfaction to measure product health.

What metrics should I track for diagnosing retention drops and conversion bottlenecks?

To diagnose retention drops and conversion bottlenecks, track L2 diagnostic metrics and funnel checkpoints segmented by cohort analysis to identify exactly where users churn or stall in the user journey.

How do I design a dashboard that drives product decisions instead of just showing vanity numbers?

Design actionable dashboards by applying layout principles that include clear context, baseline or target trend comparisons, visual status indicators, and strict alert hygiene to highlight metric changes requiring product decisions.

Can I use this approach to set OKRs and structure weekly metric reviews for my team?

Yes, you can set OKRs and structure reviews by aligning measurable key results to your North Star, then generating templates and cadences for weekly checks, monthly metric reviews, and quarterly business reviews to tie data to decisions.

Do I need event instrumentation data to run cohort analysis and funnel tracking?

Yes, reliable event instrumentation and analytics data are required prerequisites to power cohorting and funneling capabilities, enabling accurate trend comparisons against baselines for your product metrics.

What is the best way to align cross-functional teams around product metrics?

The best way to align cross-functional teams around product metrics is establishing a metric hierarchy from the North Star down to L1 health indicators and L2 diagnostics, ensuring everyone references measurable outcomes instead of vanity numbers.