[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AVKX5A7WHG8K1RTKJJBQ0":3,"skill-same:01M71AVKX5A7WHG8K1RTKJJBQ0":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M71AVKX5A7WHG8K1RTKJJBQ0","retention-strategy",null,"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.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fstrategies\u002Flaunch\u002Fretention\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"strategy","retention strategy","retention","marketing","at","funnel","churn prevention","customer","plan","loyalty","program","growth","reduce","when","use","improve","lifecycle","churn","for","risk","2026-11-10 10:12:30",false,"---\nname: retention-strategy\ndescription: 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.\nmetadata:\n  version: 1.1.1\n---\n\n# Strategies: Retention\n\nGuides 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.\n\n**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.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read Sections 4 (Audience), 9 (Documentation).\n\nIdentify:\n1. **Churn type**: Voluntary (active cancel) vs involuntary (payment failure)\n2. **Signals**: Login frequency, feature usage, support tickets\n3. **Stage**: Onboarding, expansion, renewal\n\n## Churn Types\n\n| Type | Share | Causes |\n|------|-------|--------|\n| **Voluntary** | 60–80% | Pricing, missing features, poor onboarding, relationship |\n| **Involuntary** | 20–40% | Payment failures, expired cards, billing |\n\n**Predictability**: Most churn is predictable 30–90 days before cancellation via behavioral signals.\n\n## Proactive vs Reactive\n\n| Approach | Conversion |\n|----------|------------|\n| **Reactive** (after cancel) | 15–20% |\n| **Proactive** (before decision) | 60–80% |\n\nMove from lagging indicator to early warning systems.\n\n## Retention Strategies\n\n| Strategy | Use |\n|----------|-----|\n| **Health scoring** | Behavioral + transactional + relationship signals |\n| **Loyalty programs** | 5–15 percentage point retention lift |\n| **Segmentation** | Predictive modeling for at-risk |\n| **Onboarding** | Prevent low value realization early |\n| **Dunning** | Retry logic; pre-expiry card updates for involuntary |\n\n## User Value & Feedback\n\n| Dimension | Use |\n|-----------|-----|\n| **Product value** | Registration; feature usage; payment |\n| **Marketing value** | Testimonials; customer stories; webinar guests; feedback, bug reports, feature requests |\n| **Feedback analysis** | Email, community, reviews—AI-assisted analysis; prioritize by impact; route to product vs ops |\n\n**Avoid**: Treating users only as MAU\u002Fregistration denominators. See **creator-program** for creator ecosystem.\n\n## Lifecycle Integration\n\nRetention occurs after conversion; ongoing investment in customer success, not isolated campaigns. Map touchpoints: onboarding → adoption → expansion → renewal.\n\n## Output Format\n\n- **Churn analysis** (voluntary vs involuntary; signals)\n- **Retention tactics** (by stage)\n- **Health score** framework (if applicable)\n- **Intervention** playbook (at-risk triggers)\n\n## Related Skills\n\n- **email-marketing**: Onboarding sequences; win-back campaigns\n- **pmf-strategy**: Retention as PMF signal; churn as anti-signal\n- **cold-start-strategy**: First users; differs from retention\n- **analytics-tracking**: Usage data; churn signals\n- **traffic-analysis**: Attribution; retention cohort analysis\n","# Strategies: Retention\n\nGuides 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.\n\n**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.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read Sections 4 (Audience), 9 (Documentation).\n\nIdentify:\n1. **Churn type**: Voluntary (active cancel) vs involuntary (payment failure)\n2. **Signals**: Login frequency, feature usage, support tickets\n3. **Stage**: Onboarding, expansion, renewal\n\n## Churn Types\n\n| Type | Share | Causes |\n|------|-------|--------|\n| **Voluntary** | 60–80% | Pricing, missing features, poor onboarding, relationship |\n| **Involuntary** | 20–40% | Payment failures, expired cards, billing |\n\n**Predictability**: Most churn is predictable 30–90 days before cancellation via behavioral signals.\n\n## Proactive vs Reactive\n\n| Approach | Conversion |\n|----------|------------|\n| **Reactive** (after cancel) | 15–20% |\n| **Proactive** (before decision) | 60–80% |\n\nMove from lagging indicator to early warning systems.\n\n## Retention Strategies\n\n| Strategy | Use |\n|----------|-----|\n| **Health scoring** | Behavioral + transactional + relationship signals |\n| **Loyalty programs** | 5–15 percentage point retention lift |\n| **Segmentation** | Predictive modeling for at-risk |\n| **Onboarding** | Prevent low value realization early |\n| **Dunning** | Retry logic; pre-expiry card updates for involuntary |\n\n## User Value & Feedback\n\n| Dimension | Use |\n|-----------|-----|\n| **Product value** | Registration; feature usage; payment |\n| **Marketing value** | Testimonials; customer stories; webinar guests; feedback, bug reports, feature requests |\n| **Feedback analysis** | Email, community, reviews—AI-assisted analysis; prioritize by impact; route to product vs ops |\n\n**Avoid**: Treating users only as MAU\u002Fregistration denominators. See **creator-program** for creator ecosystem.\n\n## Lifecycle Integration\n\nRetention occurs after conversion; ongoing investment in customer success, not isolated campaigns. Map touchpoints: onboarding → adoption → expansion → renewal.\n\n## Output Format\n\n- **Churn analysis** (voluntary vs involuntary; signals)\n- **Retention tactics** (by stage)\n- **Health score** framework (if applicable)\n- **Intervention** playbook (at-risk triggers)\n\n## Related Skills\n\n- **email-marketing**: Onboarding sequences; win-back campaigns\n- **pmf-strategy**: Retention as PMF signal; churn as anti-signal\n- **cold-start-strategy**: First users; differs from retention\n- **analytics-tracking**: Usage data; churn signals\n- **traffic-analysis**: Attribution; retention cohort analysis\n",{"name":5,"metadata":44,"description":7},{"version":45},"1.1.1","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fstrategies\u002Flaunch\u002Fretention",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-13 15:29:19",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add ariadoss\u002Fsuperskills --skill retention-strategy",{"tool":62,"command":63},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill retention-strategy",{"tool":65,"command":66},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill retention-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fstrategies\u002Flaunch\u002Fretention\u002FSKILL.md",true,[],[71,98,121,140,169,185],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":39},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[73,83,84,85,86,87,88,89,90,32,91,92,93,94,95,33,96,97],"user","download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":39},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[105,27,86,106,107,108,109,110,111,32,112,113,114,115,116,37,117,118,119,120],"write plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":39},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[123,128,129,130,33,131,132,133,134,135,136,107,137,32,138,139],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":39},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发",[150,151,152,153,154,155,156,157,158,32,159,160,161,162,163,164,165,166,167,168],"web","perf","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":39},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[171,115,176,177,136,107,178,179,32,180,33,181,182,183,184],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":39},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[192,193,194,195,196,197,198,32,199,33,200],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]