churn-analysis

churn-analysis is a skill for Claude Code, Codex from w95/awesome-claude-corporate-skills. It costs 24 tokens per session (4,325 once invoked), scanned A, original, MIT.

A guide to studying customer churn, meaning when customers stop using or paying for a product, and finding accounts that may leave.

In plain words
What is it for?
It is for calculating churn measures, finding patterns, identifying at-risk accounts, and creating customer-retention plans.
Why use it?
It helps teams spot warning signs early instead of reacting only after a customer has cancelled.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit It is for calculating churn measures, finding patterns, identifying at-risk accounts, and creating customer-retention plans.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/w95/awesome-claude-corporate-skills/churn-analysis
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add w95/awesome-claude-corporate-skills --skill churn-analysis
Clone the repo
git clone --depth 1 https://github.com/w95/awesome-claude-corporate-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for churn-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/churn-analysis/github.svg)](https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/churn-analysis)
Your own site
<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/churn-analysis"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/churn-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for churn-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/churn-analysis"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/churn-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,325 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.04325
Opus 5 $0.00012 $0.02162
Sonnet 5 $0.00005 $0.00865
Haiku 4.5 $0.00002 $0.00432

Measured 9d ago against content hash d08b19e50c0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

churn-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

11-customer-success/churn-analysis/SKILL.md · 517 lines

How it starts

The opening of the file, as written. The whole thing — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Churn Analysis

Overview

Master churn prediction and prevention by analyzing churn patterns, identifying at-risk accounts before they leave, and executing targeted retention strategies. Effective churn analysis turns data into actionable retention playbooks.

Churn Metrics & Definitions

1. Core Churn Metrics

Churn Rate Calculation:

Monthly Churn Rate = (Customers Lost During Month / Starting Customers) × 100

EXAMPLE:
Starting customers (Jan 1): 200
New customers (Jan): 30
Customers churned (Jan): 5
Ending customers (Jan 31): 225

Monthly Churn Rate = (5 / 200) × 100 = 2.5%

INTERPRETATION:
2.5% monthly churn = 30% annual churn (if consistent)
This is high for SaaS (1-2% monthly is typical)

Related Metrics:

  • Net Churn: Revenue churn accounting for expansion revenue
  • Logo Churn: Number of customers (what we calculated above)
  • Revenue Churn: Dollar value of lost contracts
  • Cohort Churn: Churn by customer acquisition cohort (e.g., Q1 2023 cohort)
  • Involuntary Churn: Payment failures, non-renewal (vs. voluntary cancellation)

2. Churn Types

VOLUNTARY CHURN (Customer actively leaves):
- Reason: Found better product
- Reason: No longer need capability
- Reason: Switching to competitor
- Reason: Budget cuts
- Typical Rate: 60-70% of total churn
- Intervention: Retention playbook, win-back campaign

INVOLUNTARY CHURN (Payment/technical failure):
- Reason: Payment card declined
- Reason: Non-renewal (contract expired; didn't renew)
- Reason: Delinquent account suspended
- Typical Rate: 30-40% of total churn
- Intervention: Payment processing fix, renewal reminder system

EXPECTED CHURN (Company context):
- Reason: Customer bankruptcy
- Reason: Customer acquires competitor
- Reason: Use case no longer relevant
- Typical Rate: 5-10% of total churn
- Intervention: None; expected; document reason

Churn Analysis Framework

Step 1: Segment Churn by Dimension

Analyze Churn by Customer Segment:

CHURN ANALYSIS BY SEGMENT

Segment | Customers | Churned | Churn Rate | Annual Impact
---------|-----------|---------|-----------|---------------
Enterprise | 25 | 1 | 4% | $250K revenue at risk
Mid-Market | 75 | 3 | 4% | $150K revenue at risk
SMB | 200 | 15 | 7.5% | $200K revenue at risk
Startup | 50 | 8 | 16% | $100K revenue at risk
TOTAL | 350 | 27 | 7.7% | $700K revenue at risk

FINDINGS:
- Startup segment is bleeding (16% churn; disproportionate)
- SMB and Enterprise churn rates similar (4-7.5%)
- SMB represents lowest revenue but highest volume
- Startups likely have cash flow issues (expected churn)

ACTIONABLE INSIGHT:
Focus retention efforts on Startup segment (highest churn);
likely to improve with targeted intervention

Read the full file on GitHub · 517 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 517 lines · 24 tokens per session scan A d08b19e50c0b

Subscribe to this mod's changes

churn-analysis is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 4,325 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories