churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%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.

A comprehensive, highly actionable churn-prevention skill whose domain-specific tables and sequences earn their token cost. Its main weakness is the absence of explicit validation/verification checkpoints in the build workflows for batch subscriber-affecting operations.

Suggestions

Add an explicit validation checkpoint to the cancel-flow build workflow, e.g. 'Before full rollout: test the flow on a small segment and confirm save-rate tracking fires correctly; only then enable for all subscribers.'

Add a verify step to the dunning setup workflow, e.g. 'After configuring retries and emails: trigger a test failed payment end-to-end and confirm each dunning email fires at the intended cadence before going live.'

Trim the opening role-play sentence ('You are an expert in SaaS retention and churn prevention...') since it states intent Claude can infer from the skill's purpose, slightly improving conciseness.

Dimension	Reasoning	Score
Conciseness	The body is information-dense with domain-specific data (offer-to-reason mappings, retry timing, recovery benchmarks) that Claude would not already know, but the opening role-play line 'You are an expert in SaaS retention and churn prevention' and a few explanatory prose passages could be trimmed.	4 / 5
Actionability	Highly concrete guidance throughout: specific discount ranges ('20-30% off for 2-3 months'), retry timing schedules, a full dunning email sequence with timing/tone/content, a weighted health-score formula, and named CLI tools (stripe, customer-io, posthog) covering the common cases.	5 / 5
Workflow Clarity	The cancel flow (Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel) and dunning stack are clearly sequenced, but there are no explicit build-time validation or verification checkpoints for these batch, subscriber-affecting operations, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	Two real one-level-deep references are clearly signaled ('see references/cancel-flow-patterns.md', 'see references/dunning-playbook.md'), both verified to exist, with the strategy overview kept inline and provider-specific detail appropriately offloaded.	5 / 5
	Total	17 / 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.

An excellent description that concretely states capabilities, provides comprehensive natural trigger terms, answers both what and when explicitly, and actively disambiguates from neighboring skills. It uses appropriate third-person/impersonal voice.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions — 'reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what (the five actions) and when ('When the user wants to...', 'Also use when the user mentions...', 'Use this whenever someone is losing subscribers'), with concrete trigger phrases throughout.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms (churn, cancel flow, offboarding, save offer, dunning, win-back, retention) and user-voice phrasings ('people keep canceling', 'churn rate is too high', 'how do I keep users', 'customers are leaving').	5 / 5
Distinctiveness Conflict Risk	Occupies a clear churn/retention niche with distinct triggers and explicit disambiguation routing overlap cases away ('For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.'), minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: joshmanders/dotfiles
Path: claude/skills/churn-prevention/SKILL.md
Commit: 54ab5f6

Reviewed: 4 days 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.