metrics-review

Analyze product metrics trends and anomalies into a decision-ready scorecard.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill metrics-review-ngochuy13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metrics-review
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/metrics-review
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill metrics-review-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you interpret product metrics so you can quickly understand what changed, why it may have changed, and what to do next.

Core Features & Use Cases

  • Metrics trend analysis: Compare current metrics against previous periods and targets to identify improvements or regressions.
  • Structured scorecards: Produce a clear metric scorecard with status (on track, at risk, miss) for fast scanning.
  • Actionable investigation plan: Translate findings into specific follow-up questions, recommended analyses, experiments, and monitoring/alert ideas.
  • Common review workflows: Weekly, monthly, quarterly metrics check-ins; incident or anomaly response; target vs performance gap analysis.

Quick Start

Run /metrics-review for the last quarter to generate a metrics review summary, scorecard, trend explanations, bright spots, areas of concern, and recommended next actions.

Frequently Asked Questions about metrics-review

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

FAQPage Schema
How do I turn raw product metrics into a decision-ready scorecard?

To turn raw product metrics into a decision-ready scorecard, you analyze trends, anomalies, and target deviations. This process organizes numbers by a North Star/L1/L2 hierarchy to output a clear scorecard with status indicators, insights, and recommended actions.

What is the best way to investigate metric spikes or drops during a business review?

The best way to investigate metric spikes or drops is by applying segmentation and correlation analysis to your product metrics. This identifies anomaly drivers and deviations from targets, translating the findings into a structured investigation plan with follow-up questions and recommended experiments.

How do I structure weekly or quarterly metrics check-ins against OKR targets?

You structure weekly or quarterly metrics check-ins by comparing current performance against previous periods and OKR targets. Organizing metrics into a North Star/L1/L2 hierarchy allows you to quickly generate a summary, identify bright spots and areas of concern, and track goal progress.

Can I analyze segment drivers and correlations without predefined metric hierarchies?

Analyzing segment drivers and correlations requires a predefined North Star/L1/L2 metric hierarchy. Without this structured framework, the metrics review cannot accurately map correlations, identify segment deviations from targets, or output a focused scorecard with actionable insights.

What limitations exist when comparing product performance against goals using this approach?

A limitation when comparing product performance against goals is that the analysis outputs caveats alongside recommended actions. The scorecard relies strictly on the provided metric hierarchy and segmentation data, meaning incomplete input datasets will limit the accuracy of trend explanations and anomaly investigations.