agentleFS
Sign inStart free
About-IntelligenceAbout-Intelligence/awesome-marketing-skills/skills/cohort-analysis/SKILL.md

cohort-analysis

Skill14 starsChanged 8 months agoMITView on GitHub

Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights.

20 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-experiments-existing, brainstorm-ideas-new and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    brainstorm-experiments-existing

    Design 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.

    Also in 4 projects that use this

  • skytiger6724Skill

    brainstorm-ideas-new

    Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.

    Also in 4 projects that use this

  • 45ckSkill

    pestle-analysis

    Also in 4 projects that use this

  • +4 more from skytiger6724

The file

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 14 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
  1. Distinctive:

    Verify data structure: cohort identifier, time periods, engagement metrics

    line 27
  2. Distinctive:

    Check for missing values and data quality issues

    line 28
  3. Distinctive:

    Create line charts showing cohort progression

    line 40
  4. Distinctive:

    Data Reading: Import CSV, Excel, JSON, SQL query results

    line 91
  5. Distinctive:

    Visualizations: Create heatmaps, charts, and interactive dashboards

    line 96
  6. Distinctive:

    Request specific output: Ask for visualizations, Python scripts, or research recommendations

    line 107

“Common” is measured: kept by at least 6 in 10 of the 14 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free