Works with
Packaged from the source skill for Claude, Codex and 4 more.
What this skill does
Turn cancellation reasons, subscription metrics and billing constraints into a retention plan covering cancel flows, save offers, customer risk signals and failed-payment recovery.
Workflow and deliverables
The workflow separates voluntary churn from payment failures, maps offers to reasons for leaving, and defines cohort metrics and experiments. The package includes cancel-flow patterns and a dunning playbook.
Requirements and limits
Requires real billing and usage data; offer economics, cancellation rights and billing-provider implementation still need review. It does not guarantee a recovery rate.
What is inside the skill
Section headings from the original SKILL.md (about 2,661 words of instructions). Read the full text in the source repository before installing.
- Before Starting
- 1. Current Churn Situation
- 2. Billing & Platform
- 3. Product & Usage Data
- 4. Constraints
- How This Skill Works
- Cancel Flow Design
- The Cancel Flow Structure
- Exit Survey Design
- Dynamic Save Offers
- Save Offer Types
- Cancel Flow UI Patterns
- Churn Prediction & Proactive Retention
- Risk Signals
- Health Score Model
- Proactive Interventions
- Involuntary Churn: Payment Recovery
- The Dunning Stack
- Pre-Dunning (Prevent Failures)
- Smart Retry Logic
- Dunning Email Sequence
- Recovery Benchmarks
- Metrics & Measurement
- Key Churn Metrics
Bundled files
evals/evals.jsonreferences/cancel-flow-patterns.mdreferences/dunning-playbook.mdLICENSE
Example prompts
- Design a cancellation flow for our monthly SaaS with pause and downgrade options.
- Plan a dunning sequence for Stripe subscribers whose renewal payments fail.
How to install Churn Prevention
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
Churn Prevention FAQ
What does the Churn Prevention skill do?
Turn cancellation reasons, subscription metrics and billing constraints into a retention plan covering cancel flows, save offers, customer risk signals and failed-payment recovery.
Which AI agents can use Churn Prevention?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install Churn Prevention in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made Churn Prevention and what is the license?
Churn Prevention is published by Corey Haines under the MIT license. The source is https://github.com/coreyhaines31/marketingskills/tree/main/skills/churn-prevention. The catalog keeps the original attribution.
What permissions does Churn Prevention need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.