CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, actionable retention skill with concrete benchmarks, sequenced workflows, and properly split reference files. Minor room to tighten the overview and add explicit validation checkpoints within flows.

Suggestions

Trim the opening 'You are an expert...' framing and consolidate inline tables (e.g., tool integrations) to keep SKILL.md a leaner overview.

Add explicit validation/measurement checkpoints within the cancel-flow and dunning workflows (e.g., 'verify offer acceptance is tracked before going live').

Consider moving the detailed UI mockup or health-score model into a reference file to deepen the progressive-disclosure split.

DimensionReasoningScore

Conciseness

Mostly efficient and table-driven with domain-specific benchmarks rather than padding, though the 425-line body and prose intros like 'You are an expert in SaaS retention...' could be tightened slightly.

4 / 5

Actionability

Highly concrete and executable: specific discount ranges ('20-30% off for 2-3 months'), exact retry timing ('Retry 1: 24 hours after failure'), a weighted health-score formula, and ready-to-use dunning email copy.

5 / 5

Workflow Clarity

Multi-step flows are clearly sequenced (Trigger → Survey → Offer → Confirmation; Pre-dunning → Smart retry → Dunning emails → Hard cancel) with measurement feedback in the metrics section, but explicit validation checkpoints within each flow are limited.

4 / 5

Progressive Disclosure

Good structure with well-signaled one-level-deep references to real bundle files (cancel-flow-patterns.md, dunning-playbook.md), though the SKILL.md itself is fairly dense rather than a lean overview.

4 / 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.

A strong, well-constructed description that clearly defines the skill's purpose and trigger conditions with comprehensive natural keywords and explicit boundary guidance to sibling skills. No significant weaknesses.

DimensionReasoningScore

Specificity

Lists multiple 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 states both what ('reduce churn, build cancellation flows, set up save offers...') and when ('Use when the user mentions... Use this whenever someone is losing subscribers') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms and user phrasings such as 'churn,' 'cancel flow,' 'dunning,' 'win-back,' 'people keep canceling,' and 'customers are leaving.'

5 / 5

Distinctiveness Conflict Risk

Clear churn-prevention niche with distinct triggers and explicit boundary guidance ('For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.') that minimizes conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
coreyhaines31/marketingskills
Reviewed

Table of Contents

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.