churn-prevention

Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences. Use when designing or optimizing a cancel flow, building save offers, setting up dunning emails, or reducing failed-payment churn. Trigger keywords: cancel flow, churn reduction, save offers, dunning, exit survey, payment recovery, win-back, involuntary churn, failed payments, cancel page. NOT for customer health scoring or expansion revenue — use customer-success-manager for that.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable playbook that appropriately splits detail into one-level-deep references and a runnable script. Its only weakness is mild motivational padding and the absence of an explicit error-recovery feedback loop in the workflow.

Suggestions

Trim motivational framing (e.g., 'Churn is a revenue leak you can plug... That compounds.' and 'You are an expert in SaaS retention...') to improve token efficiency, since Claude does not need this context.

Add an explicit validate→fix→retry checkpoint to at least one workflow (e.g., after launching a save offer or dunning sequence, verify save/recovery rate against the benchmark red flags and iterate) to strengthen workflow clarity.

Consider tightening the 'Before Starting' context-gathering list into a compact checklist so the opening section earns its tokens as directly as the rest of the body.

Dimension	Reasoning	Score
Conciseness	Content is mostly dense and actionable (tables, schedules, formulas), but motivational framing such as 'Churn is a revenue leak you can plug... That compounds.' and 'You are an expert in SaaS retention...' is mild padding Claude does not need.	4 / 5
Actionability	Provides copy-ready concrete guidance across the common cases — reason→offer mapping tables, an exact retry-day schedule, email subject lines with tones and CTAs, metric formulas with benchmarks, and a runnable command `python3 scripts/churn_impact_calculator.py`.	5 / 5
Workflow Clarity	The 5-stage cancel flow and three modes are clearly sequenced with an explicit confirmation checkpoint and red-flag monitoring signals, but there is no explicit validate→fix→retry feedback loop within the workflow itself.	4 / 5
Progressive Disclosure	The body stays an overview and defers full detail to clearly signaled one-level-deep links to verified files — references/cancel-flow-playbook.md and references/dunning-guide.md — plus a directly invokable script, making navigation easy.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it pairs a concrete capability statement with an explicit 'Use when' clause, a comprehensive trigger-keyword list, and a clear boundary against a sibling skill. It satisfies every completeness and distinctiveness anchor at the top level.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas — 'cancel flow design, save offers, exit surveys, and dunning sequences' — giving comprehensive coverage of what the skill does rather than vague abstractions.	5 / 5
Completeness	It clearly answers 'what' (reduce voluntary and involuntary churn via four mechanisms) and 'when' ('Use when designing or optimizing a cancel flow, building save offers, setting up dunning emails, or reducing failed-payment churn') with concrete trigger phrases.	5 / 5
Trigger Term Quality	An explicit 'Trigger keywords' clause supplies comprehensive natural terms users would say — 'cancel flow, churn reduction, save offers, dunning, exit survey, payment recovery, win-back, involuntary churn, failed payments, cancel page' — including synonyms like 'win-back' and 'payment recovery'.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (cancel flow / dunning) and explicitly disambiguates with 'NOT for customer health scoring or expansion revenue — use customer-success-manager for that', minimizing wrong-skill triggering.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: marketing-skill/skills/churn-prevention/SKILL.md
Commit: 19392f7

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.