cohort-analysis
This Claude Code skill performs cohort analysis on user engagement data by reading datasets, calculating retention rates and adoption trends, generating visualizations like retention heatmaps and comparison charts, and identifying patterns such as early churn or seasonal trends. Use it when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or discovering engagement trends across different user segments.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/cohort-analysis && cp -r /tmp/cohort-analysis/pm-data-analytics/skills/cohort-analysis ~/.claude/skills/cohort-analysisSKILL.md
# 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 - [Cohort Analysis 101: How to Reduce Churn and Make Better Product Decisions](https://www.productcompass.pm/p/cohort-analysis) - [The Product Analytics Playbook: AARRR, HEART, Cohorts & Funnels for PMs](https://www.productcompass.pm/p/the-product-analytics-playbook-aarrr) - [Are You Tracking the Right Metrics?](https://www.productcompass.pm/p/are-you-tracking-the-right-metrics)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze 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.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.