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,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

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 well-organized, highly actionable strategy skill that pushes detailed patterns and provider-specific dunning setup into real reference files. Main weaknesses are token weight from the ASCII mockup and lighter explicit validation checkpoints in the workflows.

Suggestions

Trim or collapse the full ASCII cancel-flow UI mockup into a compact reference; it consumes significant tokens for an illustrative example.

Add explicit validation/decision checkpoints to the cancel-flow and dunning sequences (e.g., 'Confirm offer rules do not violate FTC Click-to-Cancel before deploying').

Move the 'Before Starting' intake questionnaire and the tool-integration tables into a reference file to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Information-dense tables and benchmarks with little over-explanation of concepts Claude already knows, but the large ASCII UI mockup and some enumerated lists could be trimmed to tighten the token budget.

4 / 5

Actionability

Highly concrete guidance throughout — specific discount ranges (20-30% for 2-3 months), retry timing schedules, a dunning email sequence with day/tone/content, a weighted health-score formula, and recovery benchmarks make it directly actionable.

5 / 5

Workflow Clarity

Clear multi-step sequences (Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel; Pre-dunning → Smart retry → Dunning emails → Grace period → Hard cancel) with numbered steps and a retry timeline; this is design/strategy guidance so the destructive-batch validation cap does not apply, but explicit decision checkpoints are thinner.

4 / 5

Progressive Disclosure

Two real, one-level-deep reference files (references/cancel-flow-patterns.md, references/dunning-playbook.md) are clearly signaled at the ends of their relevant sections, with bulk detail pushed into them; the main file is well-sectioned though still lengthy.

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 description that covers both voluntary and involuntary churn with concrete actions, a rich set of natural trigger terms, and explicit boundary guidance to adjacent skills. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies' — with comprehensive coverage of the retention domain.

5 / 5

Completeness

Explicitly answers both 'what' ('reduce churn, build cancellation flows...') and 'when' ('When the user wants to...' / 'Also use when the user mentions...') with concrete trigger phrases, in third-person voice.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural trigger terms including synonyms and shorthand — 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'exit survey,' 'pause subscription,' 'involuntary churn.'

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct churn/retention triggers and explicit boundary disambiguation ('For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.').

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
freekmurze/dotfiles
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.