Token导航 LogoToken导航

Agent Skill · 开发

subscription-lifecycle(订阅生命周期)

subscription-lifecycle 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

subscription-lifecycle 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 3,044。

总安装 13,048周安装 533GitHub Stars 1,109下载 4,221核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/eronred/aso-skills --skill subscription-lifecycle

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。当前顶部介绍:subscription-lifecycle 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。当前底部简介为空,暂无补充说明。

来源仓库内路径:skills/subscription-lifecycle

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

subscription-lifecycle 怎么安装?

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

subscription-lifecycle 支持哪些 AI 工具?

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

subscription-lifecycle 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

subscription-lifecycle 是免费的吗?

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

subscription-lifecycle 用的人多吗?

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

subscription-lifecycle 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 来源仓库有 1,109 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

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

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
subscription-lifecycle

订阅生命周期 · 本页

13,0481,109需要联网未明确有提醒

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

SKILL.md 原文

Subscription Lifecycle

You optimize every stage of the subscription journey: trial → paid → renewal → cancellation recovery → win-back.

The Subscription Lifecycle

Install → Trial start → [Trial period] → Conversion → Renewal → ... → Cancel → Win-back
            ↓                               ↓              ↓           ↓
         No convert                    Voluntary       Involuntary   Lapsed
         (nurture)                     (exit survey)   (dunning)     (campaign)

Key Metrics at Each Stage

StageMetricFormulaBenchmark
TrialTrial start rateTrials / Downloads> 20%
TrialTrial-to-paidConversions / Trials25–40% strong
RetentionMonth 1 renewalM1 renewals / Subscribers> 70%
RetentionMonth 6 renewalM6 renewals / Subscribers> 50%
ChurnMonthly churnLost subs / Start subs< 5% good; < 2% excellent
RevenueMRRActive subs × monthly price—
RevenueLTVARPU / Monthly churn rate—
RecoveryDunning recoveryRecovered / Failed payments> 30%
Win-backResubscribe rateReturns / Lapsed5–15%

Stage 1 — Trial Optimization

Trial Length

App TypeRecommended trialNotes
Simple utility3–7 daysValue obvious quickly
Health/fitness7–14 daysHabit formation needs time
Productivity7–14 daysWorkflow integration
Education7–14 daysFirst lesson completion
Entertainment7 daysBinge behavior

Test: Monthly apps with a 7-day trial vs. 14-day trial — conversion rate may drop slightly but LTV often increases.

Trial Nurture Sequence

Send in-app (or push) messages during the trial to drive activation:

Day 0: Welcome — "Your trial has started. Here's how to get the most from it."
Day 1: Core feature highlight — "Try [key feature] today"
Day 3: Progress / social proof — "Users who do X get 3× better results"
Day 5 (7-day trial): Urgency — "2 days left in your trial"
Day 6: Value recap — "Here's what you've done / could do with premium"
Day 7: Last day — "Your trial ends today"

Rule: Messages should show value, not just create pressure.

Trial End — Conversion Moment

At trial end, show a paywall that:

  • Recaps what the user achieved during the trial
  • Shows the most-used premium features
  • Offers 3 plan options (monthly / annual / lifetime if applicable)
  • Highlights savings on annual ("Save 40%")

See monetization-strategy for paywall design details.

Stage 2 — Reducing Voluntary Churn

Why Users Cancel (and How to Fix It)

ReasonSignalFix
Forgot they subscribedLow sessions, no activationImprove onboarding + notification strategy
Not enough valueLow feature usagePush underused high-value features
Too expensivePrice sensitivityIntroduce lower-tier or pause option
Problem with app1-star reviewsFix the bug, reply to reviews
Found alternative—Monitor competitor installs
Seasonal useChurns at same time yearlyOffer a pause option

The Cancellation Flow

When a user initiates cancellation (iOS — ManagedSubscriptionGroup):

  1. Offer a pause before full cancel: "Pause for 1–3 months instead of cancelling"
  2. Show value recap: "You've used [feature] X times this month"
  3. Offer a discount: Only as last resort — 20–30% off for 3 months
  4. Exit survey: Always ask "Why are you cancelling?" (1 tap, not an essay)

Cancellation exit survey options:

  • Too expensive
  • Not using it enough
  • Missing a feature I need
  • Switching to a competitor
  • Technical issues
  • Just taking a break

Engagement Signals to Watch

Users at high churn risk:

  • Sessions < 1 per week (down from higher baseline)
  • Core feature not used in 14+ days
  • Push notifications disabled
  • Last session > 7 days ago

Trigger a re-engagement push or in-app message before they cancel.

Stage 3 — Involuntary Churn (Failed Payments)

Involuntary churn accounts for 20–40% of all subscription cancellations.

Dunning Strategy

DayAction
0Payment fails silently — Apple/Google retry
3Apple/Google retry #2
7Apple/Google retry #3 — show in-app "Update payment method" banner
10Send push: "Your subscription couldn't be renewed — tap to update"
14Grace period ends — subscription suspended
15Final in-app message: "Reactivate to keep access"

Grace period:

  • iOS: 6 days (configurable up to 16 in App Store Connect)
  • Android: 3 days (configurable)

Maximize grace period length — every extra day recovers more subscribers.

RevenueCat Integration

RevenueCat handles dunning automatically. Key settings:

  • Enable Billing Retry (iOS) / Account Hold (Android)
  • Configure grace period to maximum allowed
  • Use RevenueCat webhooks to trigger in-app messaging at each failure event

See revenuecat.md integration guide.

Stage 4 — Win-Back Campaigns

Target lapsed subscribers (cancelled or expired in last 30–90 days).

Win-Back Offer Ladder

Start with the softest offer; escalate only if no response:

Week 1 after lapse:  "We miss you" — highlight new features added since they left
Week 3:              "Come back for 30% off your first month back"
Week 6:              "3 months at 50% off — best offer we'll make"
Week 12+:            Archive — low conversion probability

Win-Back Channels

ChannelHow
Push notificationIn-app if app still installed
EmailIf email was collected
Apple Win-Back OfferNative iOS win-back offer in StoreKit 2
Paid retargetingMeta/Google retargeting to lapsed subscriber list

StoreKit 2 Win-Back Offers (iOS 18+)

Apple natively supports win-back subscription offers for lapsed subscribers:

  • Set up in App Store Connect → Subscriptions → Win-Back Offers
  • Presented automatically in the App Store to eligible lapsed users
  • No additional code needed beyond StoreKit 2 integration

Output Format

Subscription Health Report

Lifecycle Metrics ([period]):

Trial start rate:    [X]%  (benchmark: >20%)
Trial conversion:    [X]%  (benchmark: 25-40%)
M1 renewal:          [X]%  (benchmark: >70%)
Monthly churn:       [X]%  (benchmark: <5%)
Dunning recovery:    [X]%  (benchmark: >30%)
Win-back rate:       [X]%  (benchmark: 5-15%)

LTV (estimated):    $[N]
MRR:                $[N]

Top issues:
1. [Stage] — [metric] is [X]% vs benchmark [Y]% — [recommended fix]
2. [Stage] — [metric] is [X]% vs benchmark [Y]% — [recommended fix]

Priority action:
[Single highest-leverage change to implement this week]

Related Skills

  • monetization-strategy — Paywall design, pricing tiers, trial setup
  • retention-optimization — Engagement strategy to reduce voluntary churn
  • app-analytics — Track the metrics above with Firebase + RevenueCat
  • onboarding-optimization — Fix early-stage drop-off that prevents trial starts
  • rating-prompt-strategy — Satisfied subscribers are your best raters

平台分布

Codex

33.75%
按下载量换算1,425

Claude

28.65%
按下载量换算1,209

Cursor

19.89%
按下载量换算840

Gemini CLI

8.62%
按下载量换算364

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills