Skip to main content
affpapa.org
RU EN
skill CX Codex

metrics-definition — Claude Code skill: what it does, how to install

Defines UX metrics and KPIs that connect design decisions to measurable outcomes. Useful when deciding what to measure before tracking changes.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add Owl-Listener/designer-skills --skill metrics-definition -a claude-code
Open on GitHub

What metrics-definition does

The skill establishes a structured method for choosing UX metrics before measuring design changes. It groups indicators into four categories: behavioral (completion rates, task time, errors), attitudinal (SUS, NPS, CSAT), business metrics (conversion, support volume), and engagement. It also applies the HEART framework across happiness, engagement, adoption, retention, and task success.

Each metric follows a seven-part template covering name, definition, method, data source, target, frequency, and owner. The skill guides you to pick 3 to 5 primary metrics, balance behavioral data with attitudinal feedback, and record baselines before tracking differences against design hypotheses.

This skill focuses strictly on selecting indicators and planning metrics. If you need to format and present the measured outcomes later, you will need the separate design-impact-reporting skill.

What it helps with

  • select core UX metrics using the HEART framework
  • structure metric definitions with data sources and owners
  • balance behavioral and attitudinal metrics for design work
  • establish baselines before measuring design changes

Example prompts for the agent

  • Help me define 3-5 primary UX metrics for our onboarding redesign using the HEART framework
  • Create a metric definition for task completion rate using the standard template

How to install metrics-definition

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill metrics-definition -a claude-code

2Manually: put the files in place

~/.claude/skills/metrics-definition/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/metrics-definition/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about metrics-definition

How to install metrics-definition in Claude Code?

Run npx skills add Owl-Listener/designer-skills --skill metrics-definition -a claude-code.

What does metrics-definition do?

It helps teams select UX and product metrics, connect design decisions to measurable outcomes, and define indicators using the HEART framework.

What is the difference between metrics-definition and design-impact-reporting?

Use metrics-definition upfront when deciding which metrics to track. Use design-impact-reporting later to present the actual outcomes.

Source text

SKILL.md · MIT 
---
name: metrics-definition
description: Define UX metrics and KPIs that connect design decisions to measurable outcomes. Use when choosing what to measure. For presenting the results afterwards, use `design-impact-reporting` (design-ops).
---
# Metrics Definition
You are an expert in defining meaningful UX metrics that demonstrate design impact.
## What You Do
You help teams define metrics connecting design work to measurable outcomes.
## Metric Categories
- **Behavioral**: Task completion, time on task, error rate, feature adoption
- **Attitudinal**: SUS, NPS, CSAT, perceived ease of use
- **Business**: Conversion, retention, support volume, onboarding completion
- **Engagement**: DAU/MAU, session duration, feature discovery, return visits
## HEART Framework
- Happiness: satisfaction, ease ratings
- Engagement: frequency, depth
- Adoption: activation, feature uptake
- Retention: return rate, churn
- Task success: completion, time, errors
## Metric Template
Name, definition, method, data source, target, frequency, owner.
## Best Practices
- Choose 3-5 primary metrics
- Balance behavioral and attitudinal
- Set baselines before measuring change
- Connect metrics to design hypotheses
- Report alongside qualitative insights

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →
measure ghaida Defines and tracks UX metrics, experimentation frameworks, and counter-metrics. It helps teams connect design work to verifiable outcomes without metric gaming. CX Codex +1 2,700installs devrel-metrics Samuel Berthe Builds a DevRel measurement framework: 5–8 metrics with an attribution rule, a baseline, an owner and an action. Useful when the numbers grow but the budget does not. CX Codex +1 10,400installs metrics-dashboard phuryn A skill that helps you design a product metrics dashboard with North Star Metric, Input Metrics, Health Metrics, and Business Metrics. Use it when defining KPIs, setting up product analytics, or building a data monitoring plan. CX Codex +1 3,000installs metrics-review official anthropics Reviews product metrics, organizes them into an L1 and North Star hierarchy, and builds a scorecard with recommended actions. CX Codex +1 2,900installs north-star-metrics RefoundAI Walks you through auditing KPIs, choosing one North Star Metric, breaking it into input metrics and adding quality guardrails. CX Codex +1 377installs hooked-ux wondelai Scores a product's engagement loop against the Hook Model and caps designs the Manipulation Matrix calls extractive. Useful when signups stop coming back. CX Codex +1 6,200installs

From the same set109

design-review-process A skill that sets four review gates for design work, from concept to implementation QA. Useful when things ship without a consistent review step. CX Codex +1 2,000installs north-star-vision Articulates a long-horizon product vision across 1-year, 2-3 year, and 5+ year horizons. Useful when a team lacks a clear strategic direction. CX Codex +1 2,000installs test-scenario Writes usability test scenarios with realistic context, success criteria and facilitation notes. Useful once the study is planned and the tasks are still missing. CX Codex +1 2,000installs stakeholder-alignment Builds alignment artifacts: a stakeholder map, RACI matrix, decision rights and a communication plan. Useful when unclear ownership stalls decisions. CX Codex +1 2,000installs diary-study-plan Walks you through designing a diary study: prompts, cadence, duration, participant criteria and an analysis frame. CX Codex +1 2,100installs a-b-test-design Walks you through planning an A/B test: hypothesis, variants, primary metric and sample size. Useful when a change can be measured quantitatively. CX Codex +1 2,100installs form-design Designs forms end to end, covering field order, grouping, validation, and accessibility. Useful when building anything from single inputs to multi-step flows. CX Codex +1 1,900installs aesthetic-usability Applies the Aesthetic-Usability Effect when visual polish affects perceived ease of use and trust. Use it to diagnose functional designs that still make a poor first impression. CX Codex +1 1,900installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor