Improve Retention
Behavior design for user retention using B=MAP
Improve user retention by designing tiny habits using BJ Fogg's B=MAP model. This skill teaches your AI agent to reduce friction, boost motivation, and add prompts that make your product a natural part of users' daily routines.
npx skills add wondelai/skills/improve-retention --global 
Tiny Habits BJ Fogg View on Amazon
02 What it is
What is the Improve Retention skill?
Improve Retention packages BJ Fogg’s Tiny Habits, and the B=MAP model behind it, as a skill your agent loads when usage is sliding. Every behavior that failed to happen gets blamed on exactly one of three things — motivation, ability or prompt — and the fix is usually to shrink the action until it survives a bad day.
03 Key concepts
Five principles your agent applies.
Drawn from Tiny Habits — not advice it repeats back to you, but decisions it makes while it works.
04 Fit
When to use it, and
when not to.
four symptoms it fixes, and four it doesn't.
Reach for it when
Activation looks fine and week-two retention does not: people complete the core action once, then quietly stop.
Your reminder emails go out at nine in the morning to everyone, whether or not that is a moment anyone could act.
The core action takes eleven minutes and a decision, and you keep trying to solve that with more encouragement.
You are about to ship a streak counter without knowing whether the blocker is effort, timing or wanting to at all.
Reach for something else when
People leave because the product never did the job they hired it for. restart with Jobs to Be Done.
You want a compounding engagement cycle with variable rewards and investment, not one behavior made easier. use Hooked UX.
The action fails because the screen is confusing rather than effortful. UX Heuristics finds usability faults faster.
You need to know which retention number to watch and what counts as good at your stage. that is Lean Analytics.
05 Prompts
Say it like this.
Name the skill at the end of a prompt and the agent applies the framework rather than a vibe. Or say nothing — it loads on its own when a task matches.
Analyze why users drop off after signup and design habit loops using improve-retention skill
Apply B=MAP to improve daily active usage of our app using improve-retention skill
Design prompts that catch users at their highest motivation using improve-retention skill
Reduce friction in our core workflow using the Ability Chain using improve-retention skill
06 About the author
07 Same stack
The stack it sits in.
Ten Product & Innovation skills. Most people run two: this one, and whichever fits the next problem.
All Product & Innovation skills08 Questions
Before you install.
How do I install the Improve Retention skill?
Run npx skills add wondelai/skills/improve-retention --global. It takes about 30 seconds and needs no account. The Improve Retention skill then works in Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw and Hermes Agent — anything that reads the open agentskills.io format — and your agent loads it on its own when a task calls for it. It is free and MIT-licensed, and the source is at https://github.com/wondelai/skills.
Which book is the Improve Retention skill based on?
It packages Tiny Habits by BJ Fogg — founder of Stanford Behavior Design Lab. The skill distils the book's method into instructions your agent follows while it works, covering b=map model, shrink the behavior and ability chain. It sits in the Product & Innovation part of the library.
Isn’t this the same as the Hooked UX skill?
No, and the difference is diagnostic. B=MAP says a behavior occurs only when motivation, ability and a prompt converge at the same moment — so when it does not occur, precisely one of three things is missing and you go and fix that one. It is a model for behaviors that are failing, including ones that have never happened. Hooked starts from a behavior that already happens and engineers its recurrence. Different questions, and answering them in the wrong order is why so many retention projects ship a streak nobody wanted.
Why shrink the behavior instead of motivating people harder?
Because motivation is the least reliable of the three inputs. It spikes and crashes on a schedule you do not control, so any plan that requires a motivated user is a plan that works on good days only. Ability you can engineer permanently. Fogg’s Ability Chain names five links — time, money, physical effort, mental effort, and disruption to routine — and only the weakest one matters, so there is normally a single thing to fix rather than five. Shrink until the action survives a distracted Tuesday.
Tiny Habits is about personal habits — does it translate to a product?
Mostly, and the translation is what the skill does. The book’s examples are flossing and push-ups, but the mechanics port cleanly: a prompt is a notification or an existing screen, ability is your flow’s cost in time and thought, and the anchor — after I do X, I will do Y — becomes attaching your action to something the user already does. The element teams drop is celebration. Fogg argues immediate positive emotion is what wires the habit, which in software means a fast, legible confirmation rather than a silent toast.
Will this fix churn?
Only the behavioral half of it. It works on users who intend to come back and do not — forgetting, friction, bad timing — and does nothing for users who have decided the product is not worth returning to. Read your exit surveys first: “I forgot” and “too much hassle” are behavior design problems, “I did not need it” is a demand problem, and treating the second as the first buys you one month and costs you a quarter.
09 Guides that use it
Put it to work.
Long-form playbooks where this skill does part of the job.
One skill, one command.
Install Improve Retention, or the whole stack.
npx skills add wondelai/skills/improve-retention --global MIT licensed · Claude, Claude Code, Codex, Cursor, OpenClaw, Hermes · No account