retention-drop-diagnoser
Skill33 starsChanged 9 months agoMITView on GitHub
Identifies root causes behind declining user retention with likely causes, supporting evidence, and fix experiments. Use when you observe a retention drop and need to systematically diagnose why users are leaving.
Files
Retention Drop Diagnoser
Purpose
Identify root causes behind declining user retention.
Output
Retention Pattern
Likely Causes
Supporting Evidence
Fix Experiments
References
See worked example for a complete scenario.
In this repository14 other files it gives its agents.
- assumption-mapperSkill
- experiment-designSkill
- feature-adoption-analyzerSkill
- jtbd-extractorSkill
- launch-readinessSkill
- outcome-definitionSkill
- post-launch-learningSkill
- prd-criticSkill
- problem-claritySkill
- roadmap-reality-checkerSkill
- stakeholder-alignment-checkerSkill
- tradeoff-articulatorSkill
- user-segment-prioritizerSkill
- value-vs-effortSkill
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.

