/retention
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
$ npx -y skills add kostja94/marketing-skills --skill retention --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/retention
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
SKILL.md
retention.SKILL.mdname: retention-strategy
description: When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
metadata:
version: 1.1.1
Strategies: Retention
Guides customer retention and churn prevention. Acquiring new customers costs 5–25× more than retaining; 5% retention improvement can increase profitability 25–95%. Use this skill when reducing churn, building retention programs, or identifying at-risk customers.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Initial Assessment
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 4 (Audience), 9 (Documentation).
Identify: 1. **Churn type**: Voluntary (active cancel) vs involuntary (payment failure) 2. **Signals**: Login frequency, feature usage, support tickets 3. **Stage**: Onboarding, expansion, renewal
Churn Types
| Type | Share | Causes | |------|-------|--------| | **Voluntary** | 60–80% | Pricing, missing features, poor onboarding, relationship | | **Involuntary** | 20–40% | Payment failures, expired cards, billing |
**Predictability**: Most churn is predictable 30–90 days before cancellation via behavioral signals.
Proactive vs Reactive
| Approach | Conversion | |----------|------------| | **Reactive** (after cancel) | 15–20% | | **Proactive** (before decision) | 60–80% |
Move from lagging indicator to early warning systems.
Retention Strategies
| Strategy | Use | |----------|-----| | **Health scoring** | Behavioral + transactional + relationship signals | | **Loyalty programs** | 5–15 percentage point retention lift | | **Segmentation** | Predictive modeling for at-risk | | **Onboarding** | Prevent low value realization early | | **Dunning** | Retry logic; pre-expiry card updates for involuntary |
User Value & Feedback
| Dimension | Use | |-----------|-----| | **Product value** | Registration; feature usage; payment | | **Marketing value** | Testimonials; customer stories; webinar guests; feedback, bug reports, feature requests | | **Feedback analysis** | Email, community, reviews—AI-assisted analysis; prioritize by impact; route to product vs ops |
**Avoid**: Treating users only as MAU/registration denominators. See **creator-program** for creator ecosystem.
Lifecycle Integration
Retention occurs after conversion; ongoing investment in customer success, not isolated campaigns. Map touchpoints: onboarding → adoption → expansion → renewal.
Output Format
- **Churn analysis** (voluntary vs involuntary; signals)
- **Retention tactics** (by stage)
- **Health score** framework (if applicable)
- **Intervention** playbook (at-risk triggers)
Related Skills
- **email-marketing**: Onboarding sequences; win-back campaigns
- **pmf-strategy**: Retention as PMF signal; churn as anti-signal
- **cold-start-strategy**: First users; differs from retention
- **analytics-tracking**: Usage data; churn signals
- **traffic-analysis**: Attribution; retention cohort analysis
Read more
name: retention-strategy description: When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel. metadata: version: 1.1.1
Strategies: Retention
Guides customer retention and churn prevention. Acquiring new customers costs 5–25× more than retaining; 5% retention improvement can increase profitability 25–95%. Use this skill when reducing churn, building retention programs, or identifying at-risk customers.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
Initial Assessment
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 4 (Audience), 9 (Documentation).
Identify: 1. **Churn type**: Voluntary (active cancel) vs involuntary (payment failure) 2. **Signals**: Login frequency, feature usage, support tickets 3. **Stage**: Onboarding, expansion, renewal
Churn Types
| Type | Share | Causes | |------|-------|--------| | **Voluntary** | 60–80% | Pricing, missing features, poor onboarding, relationship | | **Involuntary** | 20–40% | Payment failures, expired cards, billing |
**Predictability**: Most churn is predictable 30–90 days before cancellation via behavioral signals.
Proactive vs Reactive
| Approach | Conversion | |----------|------------| | **Reactive** (after cancel) | 15–20% | | **Proactive** (before decision) | 60–80% |
Move from lagging indicator to early warning systems.
Retention Strategies
| Strategy | Use | |----------|-----| | **Health scoring** | Behavioral + transactional + relationship signals | | **Loyalty programs** | 5–15 percentage point retention lift | | **Segmentation** | Predictive modeling for at-risk | | **Onboarding** | Prevent low value realization early | | **Dunning** | Retry logic; pre-expiry card updates for involuntary |
User Value & Feedback
| Dimension | Use | |-----------|-----| | **Product value** | Registration; feature usage; payment | | **Marketing value** | Testimonials; customer stories; webinar guests; feedback, bug reports, feature requests | | **Feedback analysis** | Email, community, reviews—AI-assisted analysis; prioritize by impact; route to product vs ops |
**Avoid**: Treating users only as MAU/registration denominators. See **creator-program** for creator ecosystem.
Lifecycle Integration
Retention occurs after conversion; ongoing investment in customer success, not isolated campaigns. Map touchpoints: onboarding → adoption → expansion → renewal.
Output Format
- **Churn analysis** (voluntary vs involuntary; signals)
- **Retention tactics** (by stage)
- **Health score** framework (if applicable)
- **Intervention** playbook (at-risk triggers)
Related Skills
- **email-marketing**: Onboarding sequences; win-back campaigns
- **pmf-strategy**: Retention as PMF signal; churn as anti-signal
- **cold-start-strategy**: First users; differs from retention
- **analytics-tracking**: Usage data; churn signals
- **traffic-analysis**: Attribution; retention cohort analysis
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill

