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).
- Installs
- 647
- Last 24h
- +22
- Trending rank
- #5379
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/designer-skills --skill behavioural-analytics- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads behavioural-analytics automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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_completedmay 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. A number that survives all five is worth designing against. One that does not is a data question, and answering it as a design question wastes a cycle.
Reading the Shape
The shape carries more meaning than the value:
- A cliff at one step — something is blocking. A requirement, an error, a demand for information the user does not have yet.
- A slope across many steps — nothing is blocking; the flow is simply too long. Removing one step will move it only slightly.
- Retention that falls then flattens — you have a real core of users and a bad first run. The flat part is the product working.
- Retention that keeps falling — no core yet. Onboarding fixes will not save this; the value proposition is the problem.
- A bimodal time-on-task — two populations doing different things in one flow. Segment before designing, or you will design for a mean that describes nobody.
From Shape to Hypothesis
A hypothesis is only useful when it forbids something. "Users are confused at step three" forbids nothing. "Users abandon at step three because the address form rejects valid non-UK postcodes" predicts a specific error rate in a specific segment, and dies cleanly if that rate is flat. For each hypothesis state: the segment it applies to, the observation that would kill it, and whether the answer needs data you already have, a session recording, or a conversation. Rank by how cheaply each can be killed, not by how likely you think it is.
Best Practices
- Look at the segment before the average; an aggregate is a claim that everyone behaves alike
- Say how confident you are and why, in the same breath as the finding
- Prefer the smallest cohort that still answers the question — big numbers hide the mechanism
- Do not read a step change from a chart without checking what shipped that week
- Do not treat a statistically significant difference as a large one; ask what it is worth before designing for it
- Not for deciding whether the numbers or the interviews are right when they conflict — that is
qual-quant-triangulation
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 behavioural-analytics?
Run npx skills add https://github.com/owl-listener/designer-skills --skill behavioural-analytics in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/behavioural-analytics/ (personal) or .claude/skills/behavioural-analytics/ (project).
Which AI agents can use behavioural-analytics?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is behavioural-analytics safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains behavioural-analytics?
It is published by owl-listener in owl-listener/designer-skills. It has 647 recorded installs.
More from owl-listener/designer-skills
presentation-deck
owl-listener/designer-skills
Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.
typography-scale
owl-listener/designer-skills
Create a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use readable-measure; for judging type on an existing screen use critique-typography (visual-critique).
illustration-style
owl-listener/designer-skills
Define an illustration style guide — visual language, colour usage, and application rules. Use when commissioning or standardising illustration. For icons, use icon-system (design-systems).
visual-hierarchy
owl-listener/designer-skills
Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use critique-visual-hierarchy (visual-critique).
color-system
owl-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).
dark-mode-design
owl-listener/designer-skills
Adapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use color-system.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.