metrics

Design North Star Metrics, input metrics, and guard rails for product success dashboards.

111|73|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill metrics-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: metrics
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/metrics
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill metrics-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often ship features without measurable success criteria, making it impossible to know whether a launch worked. This Skill structures metric design so every PRD and SPEC includes a North Star Metric, supporting input metrics, and health guard rails. ## Core Features & Use Cases - North Star Metric Definition: Guides selection of a single top-level metric that reflects customer value, with templates for SaaS, marketplace, e-commerce, and developer tool business models. - Input Metric Decomposition: Derives 3-5 leading and lagging input metrics across acquisition, activation, engagement, retention, and revenue, each with owner, baseline, and target. - Health Metrics & Guard Rails: Defines thresholds and alert conditions for metrics like error rate, latency, and support tickets that must not degrade while pursuing growth. - Use Case: When writing a PRD for a new onboarding flow, use this Skill to produce a success dashboard with a primary metric, secondary metrics, and guard rails, then link them to measurable acceptance criteria in the SPEC. ## Quick Start Ask the agent to design a North Star Metric, input metrics, and guard rails for your feature and insert them into the PRD's Goals and Success Metrics section.

Frequently Asked Questions about metrics

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

FAQPage Schema
How do I define a North Star Metric for my product?▼

A North Star Metric should reflect customer value, be influenceable by the team, measurable, and comparable over time. Common examples include Weekly Active Users for SaaS, completed transactions for marketplaces, and weekly deployments for developer tools.

What are input metrics and how do they relate to a North Star Metric?▼

Input metrics are 3-5 measurable drivers that directly influence the North Star Metric, classified as leading or lagging indicators. They span acquisition, activation, engagement, retention, and revenue, each with an owner, baseline, and target.

How do I set guard rail metrics for a product launch?▼

Guard rails are health metrics with thresholds and alert conditions that must not degrade while pursuing growth, such as error rate below 0.1% or P99 latency under 500ms. Define acceptable ranges and alert triggers for each before launch.

Can metrics from this Skill be used in PRD acceptance criteria?▼

Yes, the output is designed to insert directly into a PRD's Goals and Success Metrics section and link to a SPEC's acceptance criteria. Acceptance items are phrased as measurable conditions, such as a primary metric reaching its target while guard rails stay within thresholds.

What is the difference between leading and lagging metrics?▼

Leading metrics predict future North Star movement, such as new signups or activation rate, while lagging metrics confirm outcomes after the fact, such as week-one retention. A balanced metric design includes both types.