agentsclimarketplace

Design product metrics

Skill alexe-ev/product-plugins/data-analytics/skills/design-product-metrics

Skill library for AI agents — 15 product domains, 121 skills. Tells the agent what to ask, how to reason, and what to output.

Install
npx -y skills add alexe-ev/product-plugins --skill design-product-metrics

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Define a metrics framework for a product area including primary metrics, secondary metrics, and guardrails. Use this skill when a team needs to decide what to measure and how metrics connect to goals.

SKILL.md

2.4 KB, 459 tokens by cl100k_base, as published. Nobody here has run it

Design Product Metrics

Purpose

Help teams define a coherent metrics framework that connects product decisions to measurable outcomes.

Skill type

Conceptual skill

Use this skill when

  • A product area lacks clear metrics
  • A team is starting a new product or feature and needs instrumentation guidance
  • Existing metrics are disconnected from goals or decisions
  • OKRs need to be translated into measurable product metrics

Do not use this skill when

  • Metrics are already defined and data needs to be analyzed (use analyze-funnel-retention-cohorts)
  • The goal is experiment result analysis (use experimentation skills)

Required inputs

  • Product area and context
  • Business or product goals

Optional inputs

  • Existing metrics or tracking
  • User journey or funnel map
  • OKRs
  • Data infrastructure context

Upstream context

Works best when:

  • Goals and OKRs are defined
  • Product flow is understood

If upstream context is missing

Produce a metrics design framework with placeholder categories and flag that specific metrics require goal context.

Downstream handoff

Output can feed:

  • build-decision-dashboard
  • set-goals-okrs-kpis (metrics inform KR choices)
  • define-success-metrics (experiment metrics derived from product metrics)

Instructions

  1. Map the user journey or funnel relevant to the product area.
  2. Identify the primary metric (the one metric that best reflects product success for this area).
  3. Identify secondary metrics (leading indicators, supporting signals).
  4. Define guardrail metrics (what must not degrade).
  5. Flag vanity metrics to avoid.
  6. Map each metric to a goal or OKR.
  7. Identify data requirements and instrumentation needs.

Output

Provide:

  • Primary metric with definition
  • Secondary metrics (3–5)
  • Guardrail metrics
  • Metric-to-goal mapping
  • Instrumentation requirements
  • Vanity metrics to avoid
  • Gaps in current data coverage

Risks / caveats

  • Measuring too many things dilutes focus — one primary metric per product area
  • Vanity metrics (total signups, total pageviews) feel good and mean nothing without context
  • If a metric can't inform a decision, it probably shouldn't be on the dashboard

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.