Skip to content
cccskills
FreePublished on GitHub

cohort-analysis

Analyze users grouped by signup period or another shared characteristic to compare retention and feature adoption over time. Produce charts, highlight unusual changes, and recommend follow-up research or experiments to investigate the patterns.

OriginalShow the original 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.

Works withExcel
See how to install

Good for

  • Comparing retention across signup months
  • Tracking adoption of a new feature by user group
  • Finding periods with unusual user drop-off
  • Planning interviews or experiments based on usage data

Files included (1)

  • SKILL.md4.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ab-test-analysis

FreeSummary

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills27.2KUpdated Oct 16, 2026

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills27.2KUpdated Oct 16, 2026

ansoff-matrix

FreeSummary

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills27.2KUpdated Oct 16, 2026

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills27.2KUpdated Oct 16, 2026

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills27.2KUpdated Oct 16, 2026

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills27.2KUpdated Oct 16, 2026

See all skills by phuryn

Report a problem with this skill