nemanli
- 8 skills
- 0 followers
- 5 hours ago last updated
- ▌
- ▌ Metrics Help · nemanliRouter for ambiguous metrics prompts — "metrics", "help with metrics", "where do I start?", `/metrics-help`. Asks one scoping question and points to the right skill. Fallback only — the seven content/foundation skills auto-trigger themselves; skip this one when intent fits metrics-ux, metrics-spec, metrics-instrumentation, metrics-diagnose, metrics-review, metrics-present, or metrics-basics.
- ▌ Metrics Spec · nemanli bundleWrites a measurement plan **before** the work ships — hypothesis, primary metric, counter-metric, guardrails, decision rule, sample size — so the team agrees on what "success" means before any number exists. Triggers on "measurement plan", "what counts as success?", "how will we know if this worked?", "PRD for metrics", "pre-register the analysis". Skip after data exists (use metrics-diagnose), for picking which metric to track without committing to a decision (use metrics-ux), for tracking-plan design (use metrics-instrumentation), for stakeholder communication (use metrics-present).
- ▌ Metrics Basics · nemanli bundleDefines UX measurement frameworks, terms, and philosophy when the user is learning the foundation rather than applying it — "what is HEART?", "define cohort retention", "what is MDE?", "what's a decision rule?", "why do we measure things this way?". Skip when a real situation is in mind (redesign, metric drop, stakeholder report, pre-launch plan, A/B test, tracking plan, claim review) — those go to the content skills.
- ▌ Metrics Review · nemanli bundleStress-tests a metric claim against five common failure modes — definition, sample & power, comparison, window, counter-metric — so the user can trust, distrust, or follow up on the number. Works on incoming claims (vendor case studies, PM dashboards, "industry benchmarks", leadership quotes) AND on the user's own draft before they publish. Triggers on "is this claim true?", "review this metric", "vet this benchmark", "is +15% real?", "check this case study". Skip for diagnosing a metric movement on data you own (use metrics-diagnose) or for picking metrics (use metrics-ux).
- ▌ Metrics Present · nemanli bundleTurns metric results into stakeholder-ready output — board slide, exec email, retro deck, design impact story, stakeholder defence, "how do I explain this to the CPO/board?". Translates design findings into business language, frames counter-metrics. Skip for picking metrics (use metrics-ux), for diagnosing a movement (use metrics-diagnose), for HEART definitions (use metrics-basics).
- ▌ Metrics Diagnose · nemanli bundleDiagnoses metric movements when the user has data — a number dropped/spiked/plateaued, before/after numbers, a funnel, a cohort table, or a CSV — and asks "is this real?", "why?", or "what to check next?". Skip if no data exists yet (use metrics-ux), for stakeholder communication (use metrics-present), or for pure metric definitions (use metrics-basics).
- ▌ Metrics Instrumentation · nemanli bundleDesigns the tracking plan that captures the events behind a UX metric — event names, properties, naming conventions, taxonomy, PII rules, tool-agnostic schema. Triggers on "tracking plan", "event taxonomy", "what should we log", "event naming convention", "instrumentation", "how do I capture this metric". Skip for picking which metric to track (use metrics-ux), for the broader measurement plan (use metrics-spec), for tool-specific config (the analytics vendor's docs).