churn-risk
Skill0 starsChanged 9 months agoMITView on GitHub
Score customer segments for churn risk from behavioral signals — email engagement decline, purchase recency, usage drops, support sentiment — producing a 0-100 risk scorecard with four tiers, per-tier intervention playbooks (actions, timing windows, channels, messaging), LTV-at-risk totals, and retention-ROI prioritization. Assesses and recommends; it does not send outreach or launch campaigns. Triggers on \"/digital-marketing-pro:churn-risk\", \"which customers are about to churn\", \"score our segments for churn risk\", \"email engagement is dropping, who is at risk\", \"build a retention intervention plan\". Pulls behavioral data from a connected CRM MCP (Salesforce or HubSpot) or user-provided exports, runs scripts/churn-predictor.py, and reads the brand profile for lifecycle context.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- indranilbanerjee/digital-marketing-proedited, first seen Feb 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- indranilbanerjee/digital-marketing-pro★ 93489% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository163 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ab-test-planSkill
- ad-creativeSkill
- add-integrationSkill
- aeo-auditSkill
- aeo-geoSkill
- agency-dashboardSkill
- analytics-insightsSkill
- anomaly-scanSkill
- attribution-modelSkill
- attribution-reportSkill
- audience-intelligenceSkill
- audience-profileSkill
- autopilot-statusSkill
- backlink-gapSkill
- brand-setupSkill
- budget-optimizerSkill
- budget-trackerSkill
- c2pa-metadataSkill
- campaign-auditSkill
- campaign-orchestratorSkill
- campaign-planSkill
- campaign-statusSkill
- case-study-planSkill
- checkSkill
- client-onboardingSkill
- client-proposalSkill
- client-reportSkill
- client-validation-documentSkill
- cohort-analysisSkill
- competitor-alertsSkill
- competitor-analysisSkill
- competitor-monitorSkill
- competitor-pagesSkill
- connectSkill
- content-briefSkill
- content-calendarSkill
- content-decay-scanSkill
- content-engineSkill
- content-repurposeSkill
- context-engineSkill
- continuous-improvement-loopSkill
- counter-narrativeSkill
- cowork-setupSkill
- creative-healthSkill
- creative-testing-frameworkSkill
- credential-switchSkill
- crisis-responseSkill
- crm-syncSkill
- croSkill
- dark-funnelSkill
- data-exportSkill
- data-importSkill
- digital-prSkill
- email-sequenceSkill
- emerging-channelsSkill
- engagement-workflowSkill
- entity-auditSkill
- eval-configSkill
- eval-contentSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Churn risk scorecard: All segments ranked by composite risk score — showing segment name, size, risk score (0-100), risk tier …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
/digital-marketing-pro:churn-risk
Purpose
Assess churn risk across customer segments and generate intervention strategies. Score segments using behavioral signals — email engagement decline, purchase frequency drops, login pattern changes, support ticket escalations — to categorize each segment into risk tiers and produce actionable intervention playbooks. This command bridges the gap between knowing customers are churning and knowing what to do about it. Instead of reactive "win-back" campaigns after customers have already left, it identifies at-risk segments early enough to intervene while the relationship is still recoverable. Each intervention playbook includes specific actions, timing windows, channel recommendations, and messaging approaches calibrated to the risk tier and customer value.
Input Required
The user must provide (or will be prompted for):
- Customer segments to score: The segments to evaluate — can be predefined CRM segments (e.g., "Enterprise accounts," "Monthly subscribers," "First-time buyers") or behavioral cohorts (e.g., "Users who haven't purchased in 60 days," "Users with declining email opens"). Each segment should include available behavioral signals: email engagement trends (open rate, click rate, unsubscribe rate over time), purchase frequency and recency, login or product usage patterns, support ticket volume and sentiment, and any other engagement indicators tracked in the CRM
- CRM data source: Which CRM system holds the customer data — Salesforce, HubSpot, or another connected CRM MCP. The command will pull behavioral data directly from the CRM if connected, or the user can provide exported data
- Intervention budget (optional): Total budget available for retention interventions — used to prioritize which segments and actions to focus on based on LTV-at-risk versus intervention cost. If not provided, all recommendations are generated without budget filtering
- Lookback period (optional): How far back to analyze behavioral trends — defaults to 90 days. Shorter windows catch rapid deterioration, longer windows identify slow-burn churn patterns
- Custom churn signals (optional): Brand-specific behavioral indicators beyond the defaults — e.g., "stopped using feature X," "downgraded plan tier," "removed payment method," "decreased order size" — that have historically preceded churn for this brand
Process
- Load brand context: Read
~/.claude-marketing/brands/_active-brand.jsonfor the active slug, then load~/.claude-marketing/brands/{slug}/profile.json. Apply customer lifecycle data, historical churn rates, known retention patterns, and industry benchmarks. Also check for guidelines at~/.claude-marketing/brands/{slug}/guidelines/_manifest.json— if present, load any communication frequency limits or channel restrictions that constrain intervention options. Check for agency SOPs at~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with industry defaults. - Gather customer behavioral data: Connect to the CRM MCP (Salesforce or HubSpot) and pull behavioral signal data for each segment — email engagement metrics over the lookback period, purchase history with frequency and recency calculations, product usage or login patterns, support interactions with sentiment indicators, and any custom churn signals the user specified. If CRM MCP is not connected, prompt the user to provide exported segment data or configure the integration.
- Score each segment for churn risk: Execute
python "${CLAUDE_PLUGIN_ROOT}/scripts/churn-predictor.py" --brand {slug} --action score-segment --segment-name {name} --signals '{...behavioral signals...}'with the behavioral signal data. The scoring model applies weighted signals — recent engagement decline is weighted more heavily than historical patterns, and signals are combined using a composite risk score. Each signal contributes based on its predictive strength: purchase frequency (highest weight, 0.25), engagement trend direction and velocity, support sentiment trajectory, and usage pattern breaks. Scores are normalized to 0-100 for comparability across segments. - Categorize into risk tiers: Map composite scores to four risk tiers — Low (0-25, stable engagement, no intervention needed beyond standard nurture), Medium (26-50, early warning signals present, proactive engagement recommended), High (51-75, multiple deteriorating signals, targeted intervention required within 2 weeks), and Critical (76-100, imminent churn risk, immediate high-touch intervention needed within 48 hours). These cutoffs are fixed heuristic bands, not learned from your data — the script computes the 0-100 score and these bands map score→tier. Recalibrate the band edges against your own realized churn before treating a tier as predictive; apply brand-specific thresholds where historical data suggests different cutoffs.
- Generate intervention playbook per tier: For each risk tier with active segments, create a specific intervention playbook — the actions to take (personalized outreach, special offer, product education, account review, executive touch), timing window (how quickly to act and how long the intervention sequence runs), channels to use (email, phone, in-app, direct mail based on segment preferences and tier urgency), messaging approach (tone, value proposition emphasis, urgency level), and escalation path if the initial intervention doesn't shift engagement within the defined window.
- Calculate LTV at risk: For each segment, estimate the lifetime value at risk if churn occurs — based on segment average LTV, segment size, and churn probability from the risk score. Aggregate to show total LTV at risk across all segments and per tier. This quantifies the business case for intervention investment.
- Prioritize interventions by LTV impact: Rank all interventions by the ratio of LTV-at-risk to intervention cost — high-value segments in Critical and High tiers that can be retained with relatively low-cost interventions rank highest. If the user provided an intervention budget, apply it as a constraint and show which interventions fit within budget and which require additional investment, ordered by expected retention ROI.
Output
A comprehensive churn risk assessment containing:
- Churn risk scorecard: All segments ranked by composite risk score — showing segment name, size, risk score (0-100), risk tier (Low/Medium/High/Critical), primary churn signals driving the score, and trend direction (improving, stable, or deteriorating)
- Risk tier distribution: Summary view showing how many customers and what percentage of total base fall into each tier — with comparison to industry benchmarks and the brand's historical distribution if available
- Contributing factors per segment: For each scored segment, the specific behavioral signals driving the risk assessment — which signals are deteriorating, how fast, and how they compare to the segment's historical baseline and to healthy-segment benchmarks
- Intervention playbook per tier: Detailed action plans for Medium, High, and Critical tiers — each with specific actions (what to do), timing (when to act and sequence duration), channels (where to reach them), messaging framework (what to say and how to say it), success metrics (what improvement looks like), and escalation triggers (when to escalate to the next intensity level)
- LTV at risk calculation: Total lifetime value at risk across all segments, broken down by tier — quantifying the business impact of inaction and the maximum justifiable investment in retention for each tier
- ROI estimate for intervention programs: Projected retention lift and revenue saved per intervention, based on industry retention benchmarks and the brand's historical win-back rates — showing expected ROI for each playbook to justify budget allocation
Agents Used
- marketing-scientist — Churn scoring model design with weighted behavioral signal analysis, composite risk score calculation and tier threshold calibration, LTV-at-risk estimation using segment value and churn probability, intervention prioritization by retention ROI, and statistical validation of signal predictive strength against historical churn outcomes
- crm-manager — CRM data extraction from Salesforce or HubSpot via connected MCP servers, customer segment definition and behavioral data structuring, engagement metric aggregation over lookback periods, and data quality validation to ensure scoring inputs are complete and reliable
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
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.

