← Search

Metrics definition: UX metrics and KPIs that connect design decisions to outcomes
Design 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 9a6930c
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a product or design effort whose outcomes you want…

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

At a glance
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.

Version:

Quick answer

Metrics definition is a free Muse skill helping teams define UX metrics that connect design work to measurable outcomes. It covers four categories: behavioral metrics like task completion and error rate, attitudinal metrics like SUS, NPS and CSAT, business metrics like conversion and retention, and engagement, plus the HEART framework and a metric template.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 9a6930c

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/owl-listener/designer-skills/9a6930cf84a822eb458624bd11c61aac5bbdf224/ux-strategy/skills/metrics-definition/SKILL.md Pinned version: install the code at commit 9a6930cf84a822eb458624bd11c61aac5bbdf224 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 9a6930c · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
9a6930c · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.