Churn prevention
Skill bromso/metapowers/plugins/marketing/skills/churn-prevention
A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.
npx -y skills add bromso/metapowers --skill churn-preventionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Identify and reduce churn with targeted interventions
SKILL.md
2.3 KB, 548 tokens by cl100k_base, as published. Nobody here has run it
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 $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/marketing/$ARGUMENTS/skip-log.md.
Process
-
Read context:
- Read
.metapowers/marketing/$ARGUMENTS/00-strategy.mdfor audience and product context - Read
.metapowers/marketing/$ARGUMENTS/04-engage.mdif it exists
- Read
-
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)
-
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?
-
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
-
Write the artifact — append to
.metapowers/marketing/$ARGUMENTS/04-engage.mdunder a## Churn Preventionsection:- 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