lifecycle-analyzer
Skill36 starsChanged 14 days agoMITView on GitHub
Analyze the user lifecycle — new, active, at-risk, and churned users. Use when understanding user progression, identifying at-risk users, or measuring lifecycle conversion rates.
In this repository45 other files it gives its agents.
- a11y-analyzerSkill
- annotation-opsSkill
- anomaly-detectorSkill
- api-monitorSkill
- benchmark-analyzerSkill
- campaign-trackerSkill
- changelog-detectiveSkill
- cohort-compassSkill
- comparisonsSkill
- customer-360Skill
- dashboard-builderSkill
- deploy-radarSkill
- error-forensicsSkill
- experiment-analyzerSkill
- feature-adoptionSkill
- form-analyzerSkill
- frustration-hunterSkill
- funnel-doctorSkill
- general-analysisSkill
- heatmap-generatorSkill
- incident-responderSkill
- jira-bug-reporterSkill
- journey-builderSkill
- metric-auditorSkill
- mobile-analyzerSkill
- nps-proxySkill
- onboarding-tutorSkill
- page-performanceSkill
- persona-builderSkill
- predictive-alertsSkill
- privacy-auditorSkill
- query-translatorSkill
- quick-statsSkill
- report-deckSkill
- retention-analyzerSkill
- revenue-impactSkill
- scroll-depth-analyzerSkill
- segment-wizardSkill
- session-playlistSkill
- session-reviewSkill
- session-searchSkill
- slack-reporterSkill
- user-journeySkill
- webhook-healthSkill
- weekly-digestSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Every user is in one of these lifecycle stages:
≈ “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
Lifecycle Analyzer
Map your users across the lifecycle — new, engaged, at-risk, churned — and understand what moves them from one stage to the next.
When to Use
- "How many users are at risk of churning?"
- "What percentage of new users become active?"
- "Show me the lifecycle breakdown for Q3"
- "What's the most common path from new → churned?"
- "Which lifecycle stage has the biggest drop-off?"
- "Compare lifecycle between enterprise and free users"
Mental Model
Every user is in one of these lifecycle stages:
| Stage | Definition | Segment |
| New | First session in last 7 days | first_seen in last 7 days |
| Activating | 2-5 sessions, exploring features | 2-5 sessions, first_seen in last 30 days |
| Active | Regular usage, established patterns | 6+ sessions in last 30 days |
| At-Risk | Declining usage, previously active | was active (6+ sessions) last month, <3 sessions this month |
| Churned | No activity in 30+ days | last_seen before 30 days ago |
| Resurrected | Returned after churning | last_seen before 30 days ago, but active in last 7 days |
Workflow
Step 1: Build lifecycle segments
Build one segment per stage:
fullstory:build_segment("users with first_seen in last 7 days") → new_users
fullstory:build_segment("users with 2-5 sessions and first_seen in last 30 days") → activating
fullstory:build_segment("users with 6+ sessions in last 30 days") → active
fullstory:build_segment("users with 6+ sessions last month and <3 sessions this month") → at_risk
fullstory:build_segment("users with last_seen before 30 days ago") → churnedStep 2: Measure lifecycle distribution
For each segment, get the user count:
fullstory:build_metric(query="unique users", output_type="single_number")
→ compute for each segmentPresent the distribution:
Lifecycle Distribution (Aug 2026)
New: 2,100 (14%) 🆕
Activating: 3,400 (23%) 🌱
Active: 5,800 (39%) ✅
At-Risk: 1,900 (13%) ⚠️
Churned: 1,700 (11%) 💤
Total: 14,900Step 3: Analyze stage transitions
Track how users move between stages:
New → Activating:
Of 2,100 new users in July:
- 1,400 became activating (67% activation rate)
- 700 churned immediately (33% — these are the "one-timers")Activating → Active:
Of 3,400 activating users:
- 2,100 became active (62% conversion to active)
- 800 stayed activating (still exploring)
- 500 became at-risk (lost momentum)Active → At-Risk (churn signal):
1,900 currently at-risk users:
- 1,200 were active and stopped gradually (declining sessions)
- 700 were active and stopped abruptly (possible: achieved their goal, found alternative, or had a bad experience)Step 4: Investigate transition blockers
For the biggest drop-off (New → Activating at 67%), investigate why users don't return:
fullstory:build_segment("users with 1 session, first_seen in last 30 days")
fullstory:get_sessions(segment_id, limit=10)
→ session-context: "What did this user do in their only session? Did they hit an error, get confused, or just not find what they wanted?"Step 5: Segment the lifecycle
Break down by user properties:
By plan:
Enterprise: 72% active, 8% at-risk, 4% churned
Free: 28% active, 18% at-risk, 18% churned
→ Free users are 4.5x more likely to churn. The free-to-paid conversion gap is the biggest lifecycle lever.Step 6: Report
## Lifecycle Analysis — Q3 2026
### Stage Distribution
- 14,900 total users
- Healthy ratio: 53% of users are active or activating ✅
- Watch: 13% at-risk — if half churn, that's 950 users lost this month
### Key Transitions
- New → Activating: 67% (good, but 700 one-timers/month means 8,400/year lost)
- Activating → Active: 62% (the biggest improvement opportunity — focus onboarding here)
- Active → At-Risk: 13% of active users become at-risk each month (stable rate)
### At-Risk Profile
- 1,900 at-risk users
- 63% were previously daily users → rapid disengagement
- Common last action: visited /settings or /billing → may be an account management issue
- 32% show frustration signals (rage clicks, errors) in their last 2 sessions
### Recommendations
1. Improve activation: users who complete onboarding are 3x more likely to become active. Focus on onboarding flow.
2. At-risk intervention: email users who miss 3+ consecutive days (especially daily users). Offer support.
3. Churn investigation: 700 one-timers/month. Run `session-review` on 10 one-timer sessions to understand what they saw.
### Lifecycle Funnel
New (2,100) → Activating (1,400, 67%) → Active (2,100*, 62%) → At-Risk (1,900, 13%) → Churned (1,700)
*2,100 became active this month, plus 3,700 already active = 5,800 total activeLifecycle Benchmarks
| Metric | Healthy | Concerning | Critical |
| New → Activation rate | >60% | 40-60% | <40% |
| Activation → Active rate | >50% | 30-50% | <30% |
| Active → At-Risk rate | <10% | 10-20% | >20% |
| At-Risk → Churn rate | <30% | 30-50% | >50% |
| Resurrection rate | >5% | 2-5% | <2% |
Guidelines
- Lifecycle is a model, not reality. Users don't read your lifecycle definition. Some "churned" users are on vacation. Some "at-risk" users are just busy. Use as a directional tool, not a precise measure.
- The biggest lifecycle lever is usually activation (New → Active). Users who become active in the first 30 days are 3-5x more likely to retain long-term.
- At-risk detection is most useful with an intervention. If you can't act on it (no email, no in-app message), it's just a dashboard widget. Pair with
predictive-alertsfor proactive outreach. - Segment lifecycle by acquisition channel. Users from paid ads may have different lifecycle patterns than organic users. Use
campaign-trackerto segment. - Resurrection is underrated. Users who churn and come back are often more loyal than users who never left. Track it.
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.

