Skip to content
Back to skills

Churn Prevention

ASecurity

Identify and reduce churn with targeted interventions

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add bromso/metapowers --skill churn-prevention --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Churn Prevention?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Churn Prevention
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bromso-churn-prevention/badge)](https://www.skillsdirectory.com/skills/bromso-churn-prevention)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Identify and reduce churn with targeted interventions
---

# Churn Prevention

Analyze and reduce churn for "$ARGUMENTS". Identify churn signals, design interventions, and build retention strategies.

## Prerequisites

Read `.metapowers/marketing/$ARGUMENTS/00-strategy.md`. If this file does not exist, tell the user:

> Phase 0 (Strategy) has not been completed for "$ARGUMENTS". Run `/marketing:customer-research $ARGUMENTS` first, or use `--skip-checks` to bypass.

If `--skip-checks` is present in $ARGUMENTS, skip this check and log to `.metapowers/marketing/$ARGUMENTS/skip-log.md`.

## Process

1. **Read context:**
   - Read `.metapowers/marketing/$ARGUMENTS/00-strategy.md` for audience and product context
   - Read `.metapowers/marketing/$ARGUMENTS/04-engage.md` if it exists

2. **Identify churn signals:**
   - Usage decline patterns (login frequency, feature usage drop)
   - Support ticket patterns that precede churn
   - Billing signals (failed payments, downgrade inquiries)
   - Engagement signals (email opens dropping, NPS decline)

3. **Analyze churn reasons:**
   - Use WebSearch to find common churn reasons in the category
   - Map reasons to: product gaps, pricing issues, poor onboarding, competitive switching, need ended
   - Which reasons are preventable vs. natural?

4. **Design interventions:**
   - Early warning system: automated alerts on churn signals
   - Re-engagement campaigns: email, in-app, personal outreach
   - Cancellation flow optimization: save offers, feedback collection, easy pause option
   - Win-back campaigns: timing, messaging, incentives
   - Product improvements that address top churn reasons

5. **Write the artifact** — append to `.metapowers/marketing/$ARGUMENTS/04-engage.md` under a `## Churn Prevention` section:
   - **Churn Signals** — early warning indicators to monitor
   - **Churn Reasons Analysis** — categorized and prioritized
   - **Intervention Playbook** — action per signal/reason
   - **Cancellation Flow Design** — save offers and feedback
   - **Win-Back Campaign** — timing and messaging
   - **Retention Metrics** — what to track

## Output

Churn prevention strategy written to `.metapowers/marketing/$ARGUMENTS/04-engage.md`. Present a summary highlighting:
- Top 3 churn signals to monitor
- Most impactful intervention
- Recommended cancellation flow changes

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.