agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/churn-cohort-analysis/SKILL.md

churn-cohort-analysis

Skill1 starsChanged 25 days agoMITView on GitHub

Reveals retention patterns by cohort when customer loss, contraction or renewal performance needs diagnosis.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Use when retention changes, renewal performance is unclear or acquisition cohorts appear to differ in quality.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Churn Cohort Analysis

When to use it

Use when retention changes, renewal performance is unclear or acquisition cohorts appear to differ in quality.

What Claude needs

  • Background from client-context.md
  • Customer start, renewal, cancellation and reactivation dates
  • Recurring revenue or activity by customer and period
  • Segment, product, channel and acquisition cohort fields
  • Cancellation reasons and contract terms

Method

  1. Define customer, active status, churn, contraction and reactivation rules.
  2. Reconcile opening customers or revenue through a movement bridge.
  3. Build logo and revenue retention curves by acquisition cohort.
  4. Compare patterns by tenure, segment, product and channel.
  5. Separate voluntary loss, non-payment, contraction and migration.
  6. Rank likely drivers and define targeted tests for priority cohorts.

Output format

Provide movement bridges, cohort retention tables and segment comparisons. Finish with driver hypotheses, evidence strength and test plan.

Quality checks

  • Cohort denominators remain fixed and clearly defined.
  • Reactivations and migrations are handled consistently.
  • Immature cohorts are compared only over observed periods.

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.