agentsclimarketplace

Dec product metrics

Skill jpoindexter/design-engineering-canon/skills/dec-product-metrics

20 agent-agnostic skills encoding the foundational canon of design engineering — usability heuristics, UX laws, product strategy, accessibility, performance, motion, software principles, design systems, AI-native patterns. Installs globally for Claude Code and any SKILL.md-aware agent.

Install
npx -y skills add jpoindexter/design-engineering-canon --skill dec-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

Product metrics and outcome frameworks — North Star Framework, Google HEART, AARRR (Pirate Metrics), OKRs. Use when defining what success means, choosing which metric to optimize, instrumenting a feature, or translating a goal into measurable signals instead of shipping output blindly.

SKILL.md

1.5 KB, 237 tokens by cl100k_base, as published. Nobody here has run it

Metrics & Outcomes

Frameworks to define and measure value — so you optimize outcomes, not output.

  • North Star Framework: One metric capturing the core value delivered, with input metrics that move it. Aligns the team on a single number.
  • Google HEART: Happiness, Engagement, Adoption, Retention, Task success — paired with Goals → Signals → Metrics to turn each dimension into something instrumentable.
  • AARRR (Pirate Metrics): Acquisition → Activation → Retention → Referral → Revenue. The funnel for finding where users drop.
  • OKRs: Objectives (qualitative direction) + Key Results (measurable outcomes). Outcomes, not output.

How to apply

  • Pick one North Star that genuinely reflects user value (not vanity reach); wire input metrics beneath it.
  • Use HEART → Goals/Signals/Metrics to avoid measuring what's easy instead of what matters.
  • Walk the AARRR funnel to locate the weakest stage before optimizing anything else.
  • Write Key Results as outcomes ("activation +15%"), never as shipped features ("launch X").

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.