User Cohort & Retention

Cohort Analysis & Retention Explorer

by phuryn · MIT license · ★ 26,557 on GitHub · updated Sep 14

Cohort Analysis & Retention Explorer cover

Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or…

---
name: cohort-analysis
description: "Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends."
---

# Cohort Analysis & Retention Explorer

## Purpose
Analyze user engagement and retention patterns by cohort to identify trends in user behavior, feature adoption, and long-term engagement. Combine quantitative insights with qualitative research recommendations.

## How It Works

### Step 1: Read and Validate Your Data
- Accept CSV, Excel, or JSON data files with user cohort information
- Verify data structure: cohort identifier, time periods, engagement metrics
- Check for missing values and data quality issues
- Summarize key statistics (cohort sizes, date ranges, metrics available)

Overview

You'll receive: - Data Summary: Cohort overview and data quality assessment - Quantitative Findings: Key metrics, retention rates, and trend analysis - Visualizations: Charts showing retention curves, adoption patterns - Pattern Identification: 2-3 significant insights from the data - Research Recommendations: Specific qualitative and quantitative follow-ups - Analysis Scripts (if requested): Python code for reproducible analysis - Next Steps: Prioritized actions based on findings

What you get

  • Data Summary: Cohort overview and data quality assessment

  • Quantitative Findings: Key metrics, retention rates, and trend analysis

  • Visualizations: Charts showing retention curves, adoption patterns

  • Pattern Identification: 2-3 significant insights from the data

  • Research Recommendations: Specific qualitative and quantitative follow-ups

  • Analysis Scripts: (if requested): Python code for reproducible analysis

Manual install (npx, ZIP)
Claude Codenpx skills add phuryn/pm-skills --skill cohort-analysis -g -a claude-code
Claude Code (degit)npx degit phuryn/pm-skills/pm-data-analytics/skills/cohort-analysis#main ~/.claude/skills/cohort-analysis-3
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md4.9 KB
Read SKILL.md here
phuryn/main1 file shown
SKILL.md
Show the full text115 lines

Cohort Analysis & Retention Explorer

Purpose

Analyze user engagement and retention patterns by cohort to identify trends in user behavior, feature adoption, and long-term engagement. Combine quantitative insights with qualitative research recommendations.

How It Works

Step 1: Read and Validate Your Data
  • Accept CSV, Excel, or JSON data files with user cohort information
  • Verify data structure: cohort identifier, time periods, engagement metrics
  • Check for missing values and data quality issues
  • Summarize key statistics (cohort sizes, date ranges, metrics available)
Step 2: Generate Quantitative Analysis
  • Calculate cohort retention rates and engagement trends
  • Identify retention curves, drop-off patterns, and anomalies
  • Compute feature adoption rates across cohorts
  • Calculate month-over-month or period-over-period changes
  • Generate Python analysis scripts using pandas and numpy if requested
Step 3: Create Visualizations
  • Generate retention heatmaps (cohorts vs. time periods)
  • Create line charts showing cohort progression
  • Build comparison charts for feature adoption
  • Visualize drop-off points and engagement trends
  • Output as interactive charts or static images
Step 4: Identify Insights & Patterns
  • Spot one or more significant patterns:
    • Early churn in specific cohorts
    • Late-stage engagement changes
    • Feature adoption clusters
    • Seasonal or temporal trends
  • Highlight surprising findings and deviations
  • Compare cohort performance to establish baselines
Step 5: Suggest Follow-Up Research
  • Recommend qualitative research methods:
    • Targeted user interviews with churning users
    • Feature usage surveys with engaged cohorts
    • Session replays of key interaction patterns
    • Win/loss analysis for high vs. low retention cohorts
  • Design follow-up quantitative studies
  • Suggest A/B tests or feature experiments

Usage Examples

Example 1: Upload CSV Data

Upload cohort_engagement.csv with columns: cohort_month, weeks_active,
user_id, feature_x_usage, engagement_score

Request: "Analyze retention patterns and identify why Q4 2025 cohorts
underperform compared to Q3"

Example 2: Describe Data Format

"I have monthly user cohorts from Jan-Dec 2025. Each row shows:
cohort date, user ID, purchase frequency, and support tickets.
Analyze which cohorts show best long-term retention."

Example 3: Feature Adoption Analysis

Upload feature_usage.xlsx with cohort adoption data.

Request: "Compare adoption curves for our new feature across cohorts.
Which cohorts adopted fastest? Any patterns?"

Key Capabilities

  • Data Reading: Import CSV, Excel, JSON, SQL query results
  • Retention Analysis: Calculate and visualize retention rates over time
  • Cohort Comparison: Compare metrics across cohort groups
  • Anomaly Detection: Flag unusual patterns or drop-offs
  • Python Scripts: Generate reusable analysis code for ongoing analysis
  • Visualizations: Create heatmaps, charts, and interactive dashboards
  • Research Design: Suggest targeted follow-up studies and interview approaches
  • Statistical Summary: Provide quantitative metrics and correlation analysis

Tips for Best Results

  1. Include time dimension: Provide data across multiple time periods
  2. Define cohort clearly: Make cohort grouping explicit (signup month, feature launch date, etc.)
  3. Provide context: Explain product changes, launches, or events during the period
  4. Multiple metrics: Include retention, engagement, feature usage, revenue, etc.
  5. Sufficient data: At least 3-4 cohorts for meaningful pattern identification
  6. Request specific output: Ask for visualizations, Python scripts, or research recommendations

Output Format

You'll receive:

  • Data Summary: Cohort overview and data quality assessment
  • Quantitative Findings: Key metrics, retention rates, and trend analysis
  • Visualizations: Charts showing retention curves, adoption patterns
  • Pattern Identification: 2-3 significant insights from the data
  • Research Recommendations: Specific qualitative and quantitative follow-ups
  • Analysis Scripts (if requested): Python code for reproducible analysis
  • Next Steps: Prioritized actions based on findings

Further Reading
1---
2name: cohort-analysis
3description: "Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends."
4---
5 
6# Cohort Analysis & Retention Explorer
7 
8## Purpose
9Analyze user engagement and retention patterns by cohort to identify trends in user behavior, feature adoption, and long-term engagement. Combine quantitative insights with qualitative research recommendations.
10 
11## How It Works
12 
13### Step 1: Read and Validate Your Data
14- Accept CSV, Excel, or JSON data files with user cohort information
15- Verify data structure: cohort identifier, time periods, engagement metrics
16- Check for missing values and data quality issues
17- Summarize key statistics (cohort sizes, date ranges, metrics available)
18 
19### Step 2: Generate Quantitative Analysis
20- Calculate cohort retention rates and engagement trends
21- Identify retention curves, drop-off patterns, and anomalies
22- Compute feature adoption rates across cohorts
23- Calculate month-over-month or period-over-period changes
24- Generate Python analysis scripts using pandas and numpy if requested
25 
26### Step 3: Create Visualizations
27- Generate retention heatmaps (cohorts vs. time periods)
28- Create line charts showing cohort progression
29- Build comparison charts for feature adoption
30- Visualize drop-off points and engagement trends
31- Output as interactive charts or static images
32 
33### Step 4: Identify Insights & Patterns
34- Spot one or more significant patterns:
35 - Early churn in specific cohorts
36 - Late-stage engagement changes
37 - Feature adoption clusters
38 - Seasonal or temporal trends
39- Highlight surprising findings and deviations
40- Compare cohort performance to establish baselines
41 
42### Step 5: Suggest Follow-Up Research
43- Recommend qualitative research methods:
44 - Targeted user interviews with churning users
45 - Feature usage surveys with engaged cohorts
46 - Session replays of key interaction patterns
47 - Win/loss analysis for high vs. low retention cohorts
48- Design follow-up quantitative studies
49- Suggest A/B tests or feature experiments
50 
51## Usage Examples
52 
53**Example 1: Upload CSV Data**
54```
55Upload cohort_engagement.csv with columns: cohort_month, weeks_active,
56user_id, feature_x_usage, engagement_score
57 
58Request: "Analyze retention patterns and identify why Q4 2025 cohorts
59underperform compared to Q3"
60```
61 
62**Example 2: Describe Data Format**
63```
64"I have monthly user cohorts from Jan-Dec 2025. Each row shows:
65cohort date, user ID, purchase frequency, and support tickets.
66Analyze which cohorts show best long-term retention."
67```
68 
69**Example 3: Feature Adoption Analysis**
70```
71Upload feature_usage.xlsx with cohort adoption data.
72 
73Request: "Compare adoption curves for our new feature across cohorts.
74Which cohorts adopted fastest? Any patterns?"
75```
76 
77## Key Capabilities
78 
79- **Data Reading**: Import CSV, Excel, JSON, SQL query results
80- **Retention Analysis**: Calculate and visualize retention rates over time
81- **Cohort Comparison**: Compare metrics across cohort groups
82- **Anomaly Detection**: Flag unusual patterns or drop-offs
83- **Python Scripts**: Generate reusable analysis code for ongoing analysis
84- **Visualizations**: Create heatmaps, charts, and interactive dashboards
85- **Research Design**: Suggest targeted follow-up studies and interview approaches
86- **Statistical Summary**: Provide quantitative metrics and correlation analysis
87 
88## Tips for Best Results
89 
901. **Include time dimension**: Provide data across multiple time periods
912. **Define cohort clearly**: Make cohort grouping explicit (signup month, feature launch date, etc.)
923. **Provide context**: Explain product changes, launches, or events during the period
934. **Multiple metrics**: Include retention, engagement, feature usage, revenue, etc.
945. **Sufficient data**: At least 3-4 cohorts for meaningful pattern identification
956. **Request specific output**: Ask for visualizations, Python scripts, or research recommendations
96 
97## Output Format
98 
99You'll receive:
100- **Data Summary**: Cohort overview and data quality assessment
101- **Quantitative Findings**: Key metrics, retention rates, and trend analysis
102- **Visualizations**: Charts showing retention curves, adoption patterns
103- **Pattern Identification**: 2-3 significant insights from the data
104- **Research Recommendations**: Specific qualitative and quantitative follow-ups
105- **Analysis Scripts** (if requested): Python code for reproducible analysis
106- **Next Steps**: Prioritized actions based on findings
107 
108---
109 
110### Further Reading
111 
112- [Cohort Analysis 101: How to Reduce Churn and Make Better Product Decisions](https://www.productcompass.pm/p/cohort-analysis)
113- [The Product Analytics Playbook: AARRR, HEART, Cohorts & Funnels for PMs](https://www.productcompass.pm/p/the-product-analytics-playbook-aarrr)
114- [Are You Tracking the Right Metrics?](https://www.productcompass.pm/p/are-you-tracking-the-right-metrics)
115 
View all files on GitHub →

Details

Updated
Sep 14, 2026
License
MIT
Stars on the repo
★ 26,557
Checked
Source
phuryn/pm-skills ↗
Creator
phuryn · 69 listings
View creator

Similar skills

See all →
Attribution AuditorAgriciDaniel/claude-ads · by AgriciDanielPaste the sales and spend numbers each ad platform claims, and get back a plain explanation of why they disagree and which figure to trust.★ 9.5k GitHub starsGA4 Analytics Optimizerkostja94/marketing-skills · by kostja94When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.★ 1k GitHub starsWeb Analytics Setupcoreyhaines31/marketingskills · by coreyhaines31When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.★ 51.1k GitHub starsSales Channel Attributioncoreyhaines31/marketingskills · by coreyhaines31Paste the conflicting numbers from your ad accounts, website stats and sales records; get back one honest read on which channels really drove sales and where to put your budget.★ 51.1k GitHub starsAnalytics Tracking Setupdavila7/claude-code-templates · by davila7When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.★ 32.3k GitHub starsMarketing Attribution Analystdavila7/claude-code-templates · by davila7Use when you need to model multi-touch attribution, measure marketing mix impact, validate channel performance with incrementality testing, or optimize budget allocation across paid/owned/earned channels. Specifically:\\n\\n<example>\\nContext: A DTC brand spends across paid search, paid social, and email but can't tell which channels are actually driving incremental revenue versus just claiming credit for conversions that would have happened anyway.\\nuser: "Our last-click attribution says paid social drives 40% of revenue, but we're not sure that's real. How do we find out?"\\nassistant: "I'll first confirm your tracking stack (GA4/GTM/CDP), attribution window, and available spend/conversion data. Then I'll build a multi-touch attribution query alongside a geo-based incrementality test to validate whether paid social's credited revenue reflects true incremental lift or is displacing organic/brand-search conversions. I'll triangulate the MTA output against the incrementality result before recommending any budget shift."\\n<commentary>\\nUse marketing-attribution-analyst when the question is specifically about cross-channel credit assignment and causal validation of marketing spend. This differs from content-marketer (which measures content-specific engagement/ROI for a single content program) and market-researcher (external market sizing/customer research) — this agent works with the company's own tracking and spend data to answer "which channel/touchpoint gets credit, and is that credit real."\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A mid-market SaaS company with $2M/year in marketing spend wants to move from last-click attribution to something more defensible before their next board budget review.\\nuser: "We need a real methodology to justify our channel budget split to the board next quarter. What should we actually use?"\\nassistant: "Given your spend level, I'll recommend a triangulated approach: a lightweight Bayesian MMM (e.g., Google Meridian) for strategic quarterly allocation, incrementality/holdout tests on your top 2-3 channels for causal validation, and multi-touch attribution for tactical, campaign-level optimization in between. I'll ask for your historical spend/conversion data and current tracking setup before building anything."\\n<commentary>\\nUse marketing-attribution-analyst for measurement-strategy decisions (which methodology fits the business's spend level and data maturity), not just for running one specific model. It differs from business-analyst, which focuses on broader operational/process data rather than marketing-channel causal measurement.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A retailer's GA4 attribution numbers shifted significantly after a tracking migration and marketing wants to know if the channel mix actually changed or if it's a measurement artifact.\\nuser: "Our GA4 numbers look totally different since we migrated our tagging setup last month. Did our channel mix actually shift, or is this a tracking issue?"\\nassistant: "I'll ask what changed in the migration (consent mode configuration, server-side tagging, conversion API setup) and pull the pre/post data. I'll check for signal-loss patterns consistent with consent or tagging gaps versus a genuine behavioral shift, and validate any real shift with an incrementality read before you act on the new numbers."\\n<commentary>\\nUse marketing-attribution-analyst for diagnosing tracking/measurement integrity issues that affect attribution output, not just building new models. Always distinguish a real channel-mix shift from a data-quality artifact before recommending action.\\n</commentary>\\n</example>★ 32.3k GitHub stars

More from phuryn

A/B Test Analyzerphuryn/pm-skills · by phurynAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.★ 26.6k GitHub starsFeature Request Prioritizerphuryn/pm-skills · by phurynAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.★ 26.6k GitHub starsAnsoff Matrix Generatorphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsAI Text Humanizerphuryn/work-humanizer · by phurynEdit AI-sounding text so it reads like a careful person wrote it, without changing what it says or commits to. Built for work writing where the wording matters: sales and marketing copy, support replies, HR and legal letters, emails, docs, release notes, posts, landing pages. Two modes. Rewrite: edit the text you are given. Interview: when a draft is AI-composed and thin, ask the writer 3-5 sharp questions and build the piece from their answers, in their words. Also writes from the writer's own notes or a voice-memo transcript. Calibrated on measured differences between human and AI writing.★ 110 GitHub starsMarket Segment Identifierphuryn/pm-skills · by phurynIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.★ 26.6k GitHub starsProduct Experiment Designerphuryn/pm-skills · by phurynDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.★ 26.6k GitHub stars