Token导航 LogoToken导航

Agent Skill · 研究检索

retention(retention 分析)

retention 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

retention 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,674 个 Skill 里排第 68,015。

总安装 238周安装 10GitHub Stars 168下载 83核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:retention(retention 分析)
来源仓库:https://github.com/whawkinsiv/claude-code-skills
仓库路径:skills/retention
安装命令:
npx skills add https://github.com/whawkinsiv/claude-code-skills --skill retention
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/whawkinsiv/claude-code-skills --skill retention

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

retention 用于查找、检索和筛选相关信息。适用于用户留存分析相关的数据与研究支持。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。可在多种 AI 宿主中调用,安装方式为 GitHub。建议在使用前核实其是否涉及敏感数据或外部服务调用。

retention 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/retention

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/whawkinsiv/claude-code-skills --skill retentio…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

retention 怎么安装?

在终端执行 npx skills add https://github.com/whawkinsiv/claude-code-skills --skill retention。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

retention 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

retention 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

retention 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

retention 用的人多吗?

公开数据是累计安装 238 次,近一周安装 10 次,下载 83 次,GitHub 168 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

retention 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
retention

retention 分析 · 本页

238168只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Churn Prevention & Retention

A 5% reduction in churn can increase profitability by 25-95%. This skill helps you understand why customers leave, build systems to keep them, and win back the ones you've lost.

Core Principles

  • Acquisition gets attention. Retention builds businesses. A 5% reduction in churn can increase profitability by 25-95%.
  • Churn is a symptom, not the disease. Every cancellation has a root cause you can address.
  • The best time to prevent churn is day 1. The second best time is today.
  • Retention is not one thing — it's onboarding + value delivery + relationship + habit formation.
  • For a bootstrapped founder, saving one customer is often easier and cheaper than acquiring a new one.

Understanding Your Churn

Calculate Your Churn Rate

Monthly Churn Rate = (Customers lost this month / Customers at start of month) × 100

Example: 5 cancellations / 100 customers = 5% monthly churn

Annual Churn Rate = 1 - (1 - monthly churn rate)^12

Example: 1 - (1 - 0.05)^12 = 46% annual churn (you're replacing half your base every year)

Churn Benchmarks for Bootstrapped SaaS

Monthly ChurnAnnual ChurnAssessment
< 2%< 22%Strong — you have product-market fit
2-5%22-46%Normal for early stage — room to improve
5-8%46-63%Concerning — retention is your #1 priority
> 8%> 63%Critical — fix this before spending on growth

Types of Churn

  • Voluntary churn — Customer actively cancels. They made a decision. You can learn why and sometimes prevent it.
  • Involuntary churn — Payment fails, card expires. Customer didn't choose to leave. Fix with dunning (see payments).
  • Downgrade churn — Customer moves to a lower tier or free plan. Still using the product, paying less.
  • Logo churn — Customer count. "We lost 5 customers."
  • Revenue churn — Dollar amount. "We lost $500 MRR." This matters more.

Finding At-Risk Customers

You don't need complex health scoring software. Track these signals:

Red Flags (Act Within 48 Hours)

  • Login frequency drops (was daily, now weekly, now nothing)
  • Key feature usage stops (they were using your core feature, now they aren't)
  • Support tickets increase (frustrated users complain before they leave)
  • Payment fails and isn't updated within 3 days
  • They remove team members from their account
  • They export their data

Yellow Flags (Act Within 1 Week)

  • Login frequency declining but still present
  • Only using basic features, not engaging with core value
  • Not opening your emails
  • Never upgraded from the plan they started on
  • Hasn't used a feature you shipped specifically for their use case

Simple Health Check (No Tools Needed)

For your first 100 customers, you can do this manually. Weekly:

Customer Health Review:
- [ ] Check login activity for your top 20 accounts (by revenue)
- [ ] Flag any account that hasn't logged in for 7+ days
- [ ] Check for open support tickets older than 48 hours
- [ ] Review any cancellations from the past week — email each one
- [ ] Note any accounts approaching renewal date (act 14 days before)

Preventing Churn: The Three Layers

Layer 1: Nail the First 30 Days

Most churn happens in the first 30 days. If a customer doesn't reach your "aha moment" quickly, they're gone.

  • Day 1: Welcome email + quickstart guide. Get them to one small win.
  • Day 3: Check-in email. "Did you try [core feature]? Here's how."
  • Day 7: Progress email. Show them what they've accomplished so far.
  • Day 14: Value email. "You've [metric]. Here's what power users do next."
  • Day 21: Social proof email. "Here's how [similar customer] uses [product]."
  • Day 30: Milestone email. "You've been with us a month! Here's your impact."

(See onboarding for detailed first-run guidance.)

Layer 2: Ongoing Value Delivery

After onboarding, customers need regular reminders of why they pay:

Weekly/Monthly value recap emails:

Subject: Your [Product] month in review

This month you:
- [Metric they care about, e.g., "Sent 1,247 emails"]
- [Another metric, e.g., "Saved approximately 8 hours"]
- [Usage stat, e.g., "Created 12 new campaigns"]

💡 Tip: Try [underused feature] to [benefit].

In-app nudges toward underused features:

  • If they use Feature A but never Feature B, show a contextual tooltip
  • "Did you know you can [shortcut/feature]? [CTA]"
  • Don't spam — one nudge per session max

Celebrate their wins:

  • "Congrats! You just hit 1,000 [things]."
  • "You're in the top 10% of users for [metric]."
  • Small moments of delight build emotional switching costs.

Layer 3: Relationship Building

For a solo founder with <500 customers, personal relationships are your superpower:

  • Reply to support emails personally. Sign with your first name.
  • Email your top 10 customers quarterly. "How's everything going? Anything I can build for you?"
  • Share your roadmap. "Here's what I'm building next. What matters most to you?"
  • Tell them when you ship something they asked for. "You asked for X — it's live!"
  • Be transparent about problems. "We had downtime yesterday. Here's what happened and what I'm doing to prevent it."

Cancellation Flow

When a customer clicks "Cancel," you have one last chance. Make it count:

Step 1: Ask Why (Required)

Show a cancellation reason survey before processing:

Why are you canceling?
○ Too expensive
○ Missing a feature I need: ___________
○ Switched to a competitor
○ Not using it enough
○ Technical issues
○ My needs changed
○ Other: ___________

This data is gold. Review it weekly.

Step 2: Offer an Alternative (Optional but Effective)

Based on their reason, show a targeted save offer:

ReasonCounter-Offer
Too expensiveOffer a downgrade to a cheaper plan, or a 30% discount for 3 months
Missing feature"We're building that! Want to stay on a free plan until we ship it?"
Not using it enoughOffer a pause (1-3 months) instead of cancellation
Technical issuesOffer a call to resolve their issue. Personal support from the founder
Switched to competitorAsk which one and why (learning opportunity, no save offer)

Step 3: Make Cancellation Easy

Never make cancellation frustrating. Dark patterns destroy trust and generate chargebacks. The cancel button should work. Offer alternatives, don't hide exits.

Step 4: Downgrade, Don't Delete

When a customer cancels:

  • Downgrade to free tier (if you have one) instead of deleting their account
  • Keep their data for 90 days minimum
  • This keeps the door open for return

Win-Back Campaigns

30-40% of churned customers can be won back if you approach them right:

Email Sequence

Day 1 (Cancellation):

Subject: We're sorry to see you go
Body: Quick, genuine message. No pitch. "If there's anything we could
have done better, I'd love to hear it." — [Your name]

Day 14:

Subject: Here's what's new at [Product]
Body: Share 1-2 updates shipped since they left. Show progress.

Day 30:

Subject: Want to come back? Here's 50% off for 3 months
Body: Time-limited offer. Link to reactivate with discount applied.

Day 60:

Subject: We built [feature they asked for]
Body: Only send if you actually shipped something relevant to their
cancellation reason. Include a free trial to come back and try it.

Day 90:

Subject: Last check-in from [Your name] at [Product]
Body: Final personal email. "No pressure, just wanted to let you
know the door is always open." Remove from win-back sequence.

Building Product Stickiness

Sticky products are hard to leave. Build these into your product:

Data Investment

The more data a customer puts in, the harder it is to leave:

  • Encourage custom configurations and settings
  • Make their historical data visible and valuable ("Your trends over 6 months")
  • Offer imports but make exports non-trivial (not hidden, just not one-click)

Workflow Integration

Embed in their daily workflow:

  • Integrations with tools they already use (Slack notifications, email digests)
  • Automations they set up and depend on
  • Team features (once a team uses it, no individual decides to cancel)

Habit Formation

Make your product part of their routine:

  • Daily or weekly digest emails with useful data
  • Streaks, usage milestones, or progress tracking
  • Monday morning dashboards ("Here's your week ahead")

Switching Costs (Ethical)

Not lock-in. Value that accumulates over time:

  • Reports and analytics that get better with more data
  • Templates and workflows they've customized
  • Relationships (if your product involves collaboration)

Metrics to Track

Retention Dashboard (check weekly):
- [ ] Monthly churn rate (logo and revenue)
- [ ] Churn reasons breakdown (from cancellation survey)
- [ ] Net revenue retention (revenue retained + expansion - churn)
- [ ] Time to churn (how long do customers stay on average?)
- [ ] Feature adoption rate (% of customers using core features)
- [ ] Win-back conversion rate (% of churned customers who return)

The One Metric That Matters Most

Net Revenue Retention (NRR):

NRR = (Starting MRR + Expansion - Contraction - Churn) / Starting MRR × 100

Example: ($10,000 + $500 - $200 - $800) / $10,000 = 95% NRR
  • < 90%: Revenue is shrinking even if you add new customers. Fix retention first.
  • 90-100%: Stable. New customers grow the business.
  • > 100%: Expansion revenue exceeds churn. This is the goal. Existing customers grow your revenue without new sales.

Expansion Revenue: Growing Without New Customers

The cheapest revenue is from customers who already trust you:

  • Usage-based upgrades — They hit a limit, naturally upgrade to the next tier
  • Feature upgrades — Premium features that power users need
  • Seat expansion — They add team members (each seat = more revenue)
  • Annual conversion — Monthly customers switching to annual (higher LTV, lower churn)

Tell AI:

Design an in-app upgrade prompt for [product] that triggers when a user
hits [usage limit]. Show the value of upgrading with their specific
usage data. Include a comparison of their current plan vs the next tier.
Tone: helpful, not pushy.

Common Mistakes

MistakeFix
Treating all churn the sameSegment by reason — each type needs a different response
Only measuring logo churnRevenue churn matters more. One enterprise loss > ten free-tier losses
Hiding the cancel buttonMakes users angry and generates chargebacks
No cancellation surveyYou're flying blind. Always ask why
Only emailing at risk of churnRegular value recaps prevent churn proactively
Ignoring involuntary churnFix dunning — it's 20-40% of total churn
Waiting until cancellation to actIntervene at the first red flag, not the last step

Success Looks Like

  • Monthly churn under 3% within 6 months of focused effort
  • Cancellation survey data driving your product roadmap
  • At least 20% of churned customers returning within 90 days
  • Net revenue retention above 95%
  • Customers telling you "I can't imagine going back to how I did it before"

Related Skills

  • growth — Activation and retention mechanics built into the product
  • email — Win-back sequences and engagement emails
  • feedback — Understand why customers leave through feedback systems
  • analytics — Track churn, cohort retention, and expansion revenue
  • support — Support quality directly impacts churn

平台分布

Codex

37.4%
按下载量换算31

Claude

28.66%
按下载量换算24

Cursor

18.31%
按下载量换算15

Gemini CLI

8.42%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills