Agent skill · Data & Analytics

suede-churn-prevention

Suede-owned retention discipline for voluntary and involuntary churn: cancel flows, pause paths, evidence-based save offers, failed-payment recovery, proactive signals, and win-back design. Use when diagnosing subscriber loss or designing a bounded retention intervention. NOT FOR: lifecycle-email production (use suede-emails), pricing architecture (use suede-pricing), paywall design (use suede-paywalls), or event instrumentation (use suede-analytics).

JasonColapietrogithub.com/JasonColapietroGitHub ↗
claude-codecodexMIT
Install
npx skills add JasonColapietro/suede-creator-skills --skill suede-churn-prevention --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 17 KB
Bundled scripts: none
Version: 2.0.0
Path: skills/suede-churn-prevention/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 165
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Suede Churn Prevention Use this Suede retention playbook to reduce voluntary and involuntary churn through transparent cancel flows, bounded save offers, proactive signals, and payment recovery. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): ### 1. Current Churn Situation - What's your monthly churn rate? (Voluntary vs. involuntary if known) - How many active subscribers? - What's the average MRR per customer? - Do you have a cancel flow today, or does cancel happen instantly? ### 2. Billing & Platform - What billing provider? (Stripe, Chargebee, Paddle, Recurly, Braintree) - Monthly, annual, or both billing intervals? - Do you support plan pausing or downgrades? - Any existing retention tooling? (Churnkey, ProsperStack, Raaft) ### 3. Product & Usage Data - Do you track feature usage per user? - Can you identify engagement drop-offs? - Do you have c

What's inside
Steps it walks through
  1. Before Starting
  2. 1. Current Churn Situation
  3. 2. Billing & Platform
  4. 3. Product & Usage Data
  5. 4. Constraints
  6. How This Skill Works
  7. Cancel Flow Design
  8. The Cancel Flow Structure
  9. Exit Survey Design
  10. Dynamic Save Offers
  11. Save Offer Types
  12. Cancel Flow UI Patterns
  13. Churn Prediction & Proactive Retention
  14. Risk Signals
Ships with 4 files
  • agents/openai.yaml
  • evals/evals.json
  • references/cancel-flow-patterns.md
  • references/dunning-playbook.md
More from suede-creator-skills
All skills →
About this skill
What does the suede-churn-prevention skill do?

Suede-owned retention discipline for voluntary and involuntary churn: cancel flows, pause paths, evidence-based save offers, failed-payment recovery, proactive signals, and win-back design. Use when diagnosing subscriber loss or designing a bounded retention intervention. NOT FOR: lifecycle-email production (use suede-emails), pricing architecture (use suede-pricing), paywall design (use suede-paywalls), or event instrumentation (use suede-analytics).

How do I install it?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-churn-prevention --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going