Metrics definition: UX metrics and KPIs that connect design decisions to outcomes
Define meaningful UX metrics — behavioral, attitudinal, business and engagement categories, the HEART framework, a metric template, and best practices
- What
- Define meaningful UX metrics — behavioral, attitudinal, business and engagement categories, the HEART framework, a metric template, and best practices
- Cost
- Free
- Needs
- a product or design effort whose outcomes you want to measure (the skill is a methodology the agent follows, not software to install)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @owl-listener's metrics-definition UX skill: help teams define metrics that connect design work to measurable outcomes. Covers four 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), the HEART framework (Happiness, Engagement, Adoption, Retention, Task success), a metric template (name, definition, method, data source, target, frequency, owner), and 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). Honest caveats: methodology only, no tooling; for presenting the results afterwards it points to a `design-impact-reporting` skill that is not bundled here. MIT licensed. Sibling skills from the same repo are listed separately: « owl-listener-designer-skills-competitive-analysis » and « owl-listener-designer-skills-error-handling-ux ». Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a product or design effort whose outcomes you want to measure (the skill is a methodology the agent follows, not software to install) Install "Metrics definition: UX metrics and KPIs that connect design decisions to outcomes" for me. It gives my agent @owl-listener's UX metrics framework: the four metric categories (behavioral, attitudinal, business, engagement), the HEART framework, a metric template (name, definition, method, data source, target, frequency, owner), and best practices. MIT-licensed. Repository: https://github.com/owl-listener/designer-skills/blob/main/ux-strategy/skills/metrics-definition/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). Review the files for suspicious commands or credential handling; stop on any red flag and never assume the repository is safe. Tell me if anything looks off. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "metrics-definition". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. tell the agent the design hypotheses to measure; the design-impact-reporting skill referenced for presenting results is not bundled here). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.