cohort-analysis
Skill2 starsChanged 3 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
6
Distinctive
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 15
Verify data structure: cohort identifier, time periods, engagement metrics
- Distinctive: line 16
Check for missing values and data quality issues
- Distinctive: line 28
Create line charts showing cohort progression
- Distinctive: line 79
Data Reading: Import CSV, Excel, JSON, SQL query results
- Distinctive: line 84
Visualizations: Create heatmaps, charts, and interactive dashboards
- Distinctive: line 95
Request specific output: Ask for visualizations, Python scripts, or research recommendations
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Include time dimension: Provide data across multiple time periods
- Define cohort clearly: Make cohort grouping explicit (signup month, feature launch date, etc.)
- Provide context: Explain product changes, launches, or events during the period
- Multiple metrics: Include retention, engagement, feature usage, revenue, etc.
- Sufficient data: At least 3-4 cohorts for meaningful pattern identification
- 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
Other versions19 projects use a version of this.
Word for word · 6
- skytiger6724/qwen-skills★ 2100% same
- daviszhen/agent-skills★ 1100% same
- miovrag/claude-skills★ 1100% same
- xeroc/skills★ 1100% same
- maeng777/claude-skills★ 0100% same
- stefanomartiradonna/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 13
- indranilbanerjee/digital-marketing-pro★ 920same name
- jshsakura/awesome-opencode-skills★ 30same name
- brainbytes-dev/everything-claude-marketing★ 9same name
- The-Utopia-Studio/skills★ 6same name
- NachoLafuente/5050-gtm★ 3same name
- gmanch94/claude-code-aidlc-template★ 2same name
- risadams/ink-and-agency★ 2same name
- nandanosql/all_in_one_pm_skills★ 1same name
- sidchaudhary/gtm-skills★ 1same name
- sp1e/claude-skills★ 1same name
3 more not listed
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 repository383 other files it gives its agents.
- 37signals-waySkill
- ab-test-analysisSkill
- advisor-orchestrator-workerSkill
- ai-ml-engineeringSkill
- algorithmic-artSkill
- analyze-feature-requestsSkill
- animation-vocabularySkill
- apple-designSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- improve-animationsSkill
- pick-ui-librarySkill
- prototypeSkill
- review-animationsSkill
- ansoff-matrixSkill
- api-and-interface-designSkill
- api-design-best-practicesSkill
- app-store-changelogSkill
- auth-authorizationSkill
- beachhead-segmentSkill
- blue-ocean-strategySkill
- brainstorm-experiments-existingSkill
- brainstorm-experiments-newSkill
- brainstorm-ideas-existingSkill
- brainstorm-ideas-newSkill
- brainstorm-okrsSkill
- brand-guidelinesSkill
- browser-testing-with-devtoolsSkill
- bug-hunt-swarmSkill
- business-modelSkill
- canvas-designSkill
- ci-cd-and-automationSkill
- claude-apiSkill
- clean-architectureSkill
- clean-codeSkill
- cli-creatorSkill
- code-review-and-qualitySkill
- code-review-skillSkill
- code-simplificationSkill
- cold-start-problemSkill
- commit-archaeologistSkill
- competitive-battlecardSkill
- competitor-analysisSkill
- contagiousSkill
- context-engineeringSkill
- continuous-discoverySkill
- architecture-blueprint-generatorSkill
- azure-architecture-autopilotSkill
- cli-masterySkill
- codeqlSkill
- conventional-commitSkill
- create-implementation-planSkill
- csharp-asyncSkill
- diagnoseSkill
- dotnet-best-practicesSkill
- draw-io-diagram-generatorSkill
- git-commitSkill
- github-actions-efficiencySkill
- java-springbootSkill
- mcp-cliSkill
- The first 60 shown.
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.

