Behavioural Analytics
Read funnels, retention curves, and event data as a designer — separating a design problem from a tracking artefact. Use when handed product data you did not design and asked why people drop off. For choosing what to measure, use `metrics-definition` (ux-strategy); for running a controlled test, use `a-b-test-design` (prototyping-testing).
Install
/plugin marketplace add Owl-Listener/designer-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/designer-skills --skill behavioural-analyticsgit clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/design-research/skills/behavioural-analytics ~/.claude/skills/behavioural-analyticsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Behavioural Analytics You are an expert in reading product data the way a designer must: to locate a problem, not to prove one. ## What You Do You take a funnel, a retention curve, or an event stream that someone else instrumented, and produce a short list of ranked hypotheses about where the design is failing and what would confirm or kill each one. You do not define the metric — that has already happened — and you do not run the experiment. You decide what is worth looking at next. ## Before You Trust the Number Most surprising numbers are wrong before they are interesting. Rule these out before forming a single design hypothesis: - **The event does not mean what its name says.** `checkout_completed` may fire on render, not on payment. Read the tracking definition, not the label. - **The denominator moved.** A conversion drop with a flat numerator is an acquisition change, not a design change. - **The step is not a step.** Funnels imply an order the product does not enforce. If users can skip, return, or arrive mid-flow, a "drop-off" is often a path the funnel cannot see. - **A release, a holiday, or a campaign lands on the same date.** Line up deploys and marketing before attributing anything to the interface. - **The platform split is hiding the effect.** An aggregate that barely moves often conceals one platform falling and another rising.
Details
- Skill name
behavioural-analytics- Repository
- Owl-Listener/designer-skills
- Path
design-research/skills/behavioural-analytics/SKILL.md- License
- MIT
- Repo updated
- 5 September 2026
FAQ
What does the Behavioural Analytics skill do?
Read funnels, retention curves, and event data as a designer — separating a design problem from a tracking artefact. Use when handed product data you did not design and asked why people drop off. For choosing what to measure, use `metrics-definition` (ux-strategy); for running a controlled test, use `a-b-test-design` (prototyping-testing).
How do I install the Behavioural Analytics skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Behavioural Analytics popular?
It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.
Related skills
A B Test Design
3.4kOwl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Accessibility Audit
3.4kOwl-Listener/designer-skills
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Accessibility Test Plan
3.4kOwl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Color System
3.4kOwl-Listener/designer-skills
Build a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).
Lean Analytics
2.7kwondelai/skills
Choose and audit startup metrics using Croll and Yoskovitz's "Lean Analytics". Use when the user mentions "what metrics should we track", "KPIs", "north star metric", "One Metric That Matters (OMTM)", "vanity metrics", "analytics dashboard", "DAU/MAU", "churn benchmark", or "measure product-market fit". Also trigger when choosing metrics for a startup or feature, auditing a dashboard for vanity metrics, setting metric targets and baselines, or instrumenting a product by business model and stage. Covers good-vs-vanity metrics, the One Metric That Matters, metrics by business model, the five sta
Data Visualization
3.4kOwl-Listener/designer-skills
Select chart types and design data encodings — marks, axes, labels, and accessible chart styling. Use when presenting data graphically. Owns chart selection and encoding only; the categorical colour ramp itself belongs to `color-system`.
Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.