Retention patterns
Skill Dragoon0x/product-skills/skills/growth/retention-patterns
The product thinking layer for AI agents. 580 skills. 48 commands. 8 domains. - Product strategy, discovery, execution, analytics, growth, experience, conversion, communication and more.
npx -y skills add Dragoon0x/product-skills --skill retention-patternsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 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
Design for the second visit, not just the first. Habit loops, re-engagement triggers, and value reinforcement without dark patterns. Use when retention is low, when building engagement features, or when people stop coming back.
SKILL.md
1.6 KB, as published. Nobody here has run it
Retention Patterns
Design for the second visit, not just the first.
How to use
/retention-patternsApply retention constraints to this conversation.
Constraints
Habit Loop Design
- Trigger: what brings the user back (notification, routine, need)
- Action: what they do when they return (must be low-friction)
- Reward: what value they get (must be variable, not identical every time)
- Investment: what they put in that makes the product more valuable over time (data, content, connections)
Retention Checkpoints
- Day 1: Did they experience core value?
- Day 7: Did they return without a prompt?
- Day 30: Has the product become part of a routine?
- For each checkpoint: what's the one thing that, if true, predicts long-term retention?
Re-Engagement
- MUST bring value, not just reminders ("Your weekly summary" not "We miss you")
- SHOULD trigger based on user behavior, not calendar schedules
- MUST respect opt-out preferences absolutely
- NEVER use guilt or FOMO for re-engagement
Anti-Patterns
- Streak mechanics that punish absence instead of rewarding presence
- Notifications designed to create anxiety
- Engagement features that benefit the platform but not the user
- Measuring DAU without measuring whether users got value from their visit
- Confusing addiction with loyalty