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.
npx skills add w95/awesome-claude-corporate-skills --skill churn-analysisgit clone --depth 1 https://github.com/w95/awesome-claude-corporate-skillsWrote 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.
[](https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/churn-analysis)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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
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.
- 9d ago First seen · 517 lines · 24 tokens per session scan A d08b19e50c0b
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.
Other skills, from other repositories
design-por-referencia
Use when a landing page, marketing site, or hero section looks generic/AI-made ("cara de vibe coding") and needs a $10k-agency-level redesign, or when building a new landing from scratch. Triggers - "o site ficou com cara de IA", "quero uma landing premium", "redesenha a landing", "faz o site baseado em [site de…
lighthouse-95
Use when a website must score 95+ in every Lighthouse category (Performance, Accessibility, Best Practices, SEO), when scores are stuck below target, or when diagnosing poor FCP, LCP, TBT, or CLS on a deployed site.
seo-validate
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability. Triggers: SEO, meta tags, Schema.org, hreflang, LCP, INP, CLS, Core Web Vitals, sitemap, crawlability.
debug
Systematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.
research-mastery
Hierarchical retrieval: KB → MCP/Context7 → web. Triggers: research, fact-check, verify, synthesize, cross-reference, multi-source, cite sources.