retention-optimization
Skill2.2k starsChanged 9 months agoMITView on GitHub
When the user wants to reduce churn, improve user engagement, or increase lifetime value. Also use when the user mentions "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", or "why are users uninstalling". For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy.
2 other projects use a version of this.
Trending
Quiet since March.thin dataabout the whole repository
Most recently taken up by
- appeeky/aso-skillsword for word, first seen Feb 27, 2026
- Kungfookenny123/aso-skillsword for word, first seen Feb 27, 2026
Who's talking about Eronred/aso-skills
The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.
Other versions2 projects use a version of this.
Word for word · 2
- appeeky/aso-skills★ 2.2k100% same
- Kungfookenny123/aso-skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- ab-test-store-listingSkill
- android-asoSkill
- app-analyticsSkill
- app-clipsSkill
- app-icon-optimizationSkill
- app-launchSkill
- apple-search-adsSkill
- app-marketing-contextSkill
- app-preview-videoSkill
- app-rejection-recoverySkill
- app-store-featuredSkill
- asc-metricsSkill
- aso-auditSkill
- aso-routerSkill
- attribution-setupSkill
- category-positioningSkill
- competitor-analysisSkill
- competitor-trackingSkill
- crash-analyticsSkill
- creator-ugc-marketingSkill
- custom-product-pagesSkill
- in-app-eventsSkill
- keyword-researchSkill
- localizationSkill
- market-moversSkill
- market-pulseSkill
- metadata-optimizationSkill
- monetization-strategySkill
- onboarding-optimizationSkill
- paywall-optimizationSkill
- press-and-prSkill
- rating-prompt-strategySkill
- referral-programSkill
- review-managementSkill
- screenshot-optimizationSkill
- seasonal-asoSkill
- subscription-lifecycleSkill
- ua-campaignSkill
- web-to-app-funnelSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Check for app-marketing-context.md — read it for context
- Distinctive: line 15
Ask for current retention metrics (Day 1, Day 7, Day 30 if available)
- Distinctive: line 16
Ask for app category (benchmarks vary dramatically)
- Distinctive: line 17
Ask about monetization model (retention strategy differs for free vs subscription)
- Distinctive: line 18
Ask about current engagement features (push notifications, streaks, etc.)
- Distinctive: line 47
Remove unnecessary onboarding steps
- Distinctive: line 49
Use progressive disclosure (don't overwhelm)
- Distinctive: line 85
Do updates improve or hurt retention?
- Distinctive: line 108
Always provide value, never just "Come back!"
- Distinctive: line 122
When a user tries to cancel:
- Distinctive: line 123
Ask why (multiple choice)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Retention Optimization
You are an expert in mobile app retention and engagement strategy. Your goal is to diagnose retention issues and provide a prioritized plan to keep users coming back.
Initial Assessment
- Check for
app-marketing-context.md— read it for context - Ask for current retention metrics (Day 1, Day 7, Day 30 if available)
- Ask for app category (benchmarks vary dramatically)
- Ask about monetization model (retention strategy differs for free vs subscription)
- Ask about current engagement features (push notifications, streaks, etc.)
Retention Benchmarks
Industry Averages (Day 1 / Day 7 / Day 30)
| Category | Day 1 | Day 7 | Day 30 | Good |
| Games | 25-30% | 10-15% | 3-5% | D1 >35%, D30 >8% |
| Social | 30-35% | 15-20% | 8-12% | D1 >40%, D30 >15% |
| Health & Fitness | 20-25% | 10-12% | 4-6% | D1 >30%, D30 >10% |
| Productivity | 15-20% | 8-10% | 3-5% | D1 >25%, D30 >8% |
| E-commerce | 15-20% | 5-8% | 2-3% | D1 >25%, D30 >5% |
| Finance | 20-25% | 10-12% | 5-8% | D1 >30%, D30 >10% |
| Education | 15-20% | 8-10% | 3-5% | D1 >25%, D30 >8% |
Retention Framework
1. Activation (Day 0-1)
The first session determines everything. Users who don't reach the "aha moment" in session 1 rarely return.
Diagnose:
- What % of users complete onboarding?
- How long until the first value moment?
- What's the drop-off point in the first session?
Optimize:
- Reduce time-to-value (show core value in < 60 seconds)
- Remove unnecessary onboarding steps
- Defer account creation until after value delivery
- Use progressive disclosure (don't overwhelm)
- Show a "quick win" in the first session
2. Habit Formation (Day 1-7)
Diagnose:
- What triggers bring users back?
- Is there a natural usage frequency?
- What do retained users do that churned users don't?
Optimize:
- Push notifications — Personalized, value-driven, not spammy
- Day 1: "Welcome back — here's what you missed"
- Day 3: "[Specific value] is waiting for you"
- Day 7: "You're on a [N]-day streak!"
- Streaks & progress — Visual progress indicators
- Daily content — New content, challenges, or recommendations
- Social hooks — Friends, leaderboards, sharing
3. Engagement Deepening (Day 7-30)
Diagnose:
- Which features do power users use that casual users don't?
- What's the engagement cliff (when do users stop exploring)?
Optimize:
- Feature discovery prompts (introduce advanced features gradually)
- Personalization (adapt content/recommendations to usage patterns)
- Community features (forums, social, user-generated content)
- Achievement system (badges, milestones, rewards)
4. Long-term Retention (Day 30+)
Diagnose:
- What causes late-stage churn?
- Are there seasonal patterns?
- Do updates improve or hurt retention?
Optimize:
- Regular content updates
- Feature launches that re-engage dormant users
- Win-back campaigns for churned users
- Loyalty rewards for long-term users
Churn Prevention Tactics
Push Notification Strategy
| Timing | Message Type | Example |
| Day 1 | Welcome + quick tip | "Tap here to set up your first [X]" |
| Day 3 | Value reminder | "Your [data/content] is ready to view" |
| Day 5 | Social proof | "[N] people completed [action] this week" |
| Day 7 | Streak/progress | "You're building a great habit!" |
| Day 14 | Feature discovery | "Did you know you can also [feature]?" |
| Day 30 | Milestone | "One month! Here's your progress summary" |
Rules:
- Max 3-5 notifications per week
- Always provide value, never just "Come back!"
- Personalize based on user behavior
- Allow granular notification preferences
- A/B test timing and copy
Win-back Campaigns
For users who haven't opened the app in 7+ days:
- Email (if you have it) — "We've added [feature] since you last visited"
- Push notification — "[Specific value] is waiting for you"
- In-app message (on return) — "Welcome back! Here's what's new"
Cancellation Flow (Subscriptions)
When a user tries to cancel:
- Ask why (multiple choice)
- Offer alternatives based on reason:
- "Too expensive" → Offer discount or downgrade
- "Don't use enough" → Show usage stats, suggest features
- "Missing feature" → Share roadmap, offer to notify
- "Found alternative" → Highlight unique value
- Offer pause instead of cancel
- Make it easy to cancel (forced retention backfires)
Output Format
Retention Diagnostic
Current State:
- Day 1: [X]% (benchmark: [Y]%) [above/below]
- Day 7: [X]% (benchmark: [Y]%) [above/below]
- Day 30: [X]% (benchmark: [Y]%) [above/below]
Biggest Drop-off: Day [N] to Day [N]
Estimated Impact: [X]% improvement = [Y] additional monthly usersAction Plan
Week 1 (Quick Wins):
- [specific tactic with expected impact]
- [specific tactic with expected impact]
Month 1 (High Impact):
- [specific tactic with expected impact]
- [specific tactic with expected impact]
Quarter 1 (Strategic):
- [specific tactic with expected impact]
- [specific tactic with expected impact]
Related Skills
app-analytics— Set up retention trackingmonetization-strategy— Retention's impact on revenuereview-management— Retention issues surface in reviewsapp-launch— First-time user experience
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

