Token导航 LogoToken导航

Agent Skill · 效率

subscription-renewal-health(订阅续订健康状况)

subscription-renewal-health 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

subscription-renewal-health 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 9,192。

总安装 6,286周安装 270GitHub Stars 公开资料未说明下载 2,203核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:subscription-renewal-health(订阅续订健康状况)
来源仓库:https://github.com/rijoyai/subscription-renewal-health
安装命令:
openclaw skills install subscription-renewal-health
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install subscription-renewal-health

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

用于补充效率相关能力,适合让 Agent 承接订阅续订监控类任务时使用。适用于 OpenClaw 中需要分析资金池波动、流失率或付款失败的场景。安装命令为 openclaw skills install subscription-renewal-health,建议确认权限范围。

涉及业务数据时,应先脱敏处理,防止敏感信息外泄。使用前需确认是否会触发外部服务调用,避免因权限不足导致功能失效。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install subscription-renewal-health;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

subscription-renewal-health 怎么安装?

在终端执行 openclaw skills install subscription-renewal-health。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

subscription-renewal-health 支持哪些 AI 工具?

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

subscription-renewal-health 需要什么权限?

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

subscription-renewal-health 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

subscription-renewal-health 用的人多吗?

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

subscription-renewal-health 安全吗?

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

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

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

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
subscription-renewal-health

订阅续订健康状况 · 本页

6,286—只读MIT-0通过

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

SKILL.md 原文

name
subscription-renewal-health
description
Monitor recurring-billing and subscription business health — pool volatility, churn, and payment failure — then output dunning and retention email series grounded in compensation psychology. Use when churn rate is rising, failed renewal charges or card declines spike, MRR or active subscriber count swings, dunning workflows break, or the user wants win-back and "sorry + make-good" sequences for subscribers. Automate structured reporting plus email scripts (not generic blasts). Do NOT use for one-off transactional receipts with no subscription context, or pure pricing math with no churn or payment-failure angle.
compatibility
required
[]

Subscription renewal health monitor

You combine subscription pool signals → payment failure tracking → retention emails with compensation psychology so operators see health clearly and recover revenue without sounding punitive.

When to lean in

  • Churn rate up vs prior period.
  • Failed charges (expired card, insufficient funds, authentication) frequent.
  • Volatility in active subs or MRR without clear acquisition story.

Core workflow

  1. Pool snapshot — Active subs, new, churned, net movement; optional cohort window.
  2. Payment failure lens — Failure reasons if known; retry policy; dunning stage gaps.
  3. Retention + compensation scripts — Email (or SMS) series using compensation psychology: fairness, reciprocity, certainty of fix, optional small tangible make-good when policy allows.

Gather context

  1. Platform (Stripe Billing, Recharge, Shopify Subscriptions, etc.).
  2. Churn definition (voluntary cancel vs involuntary fail).
  3. Current dunning steps and retry count.
  4. What compensation is allowed (free month, skip box, % off next cycle).

Read references/subscription_playbook.md for dunning stages and compensation framing.

Mandatory outputs (full run)

A) Health table

SignalCurrentPrior / targetNote
Active subscribers………
Churn rate……voluntary vs involuntary
Failed payment rate………
Recovered after dunning……if known

Placeholders OK; state what to export from billing tool.

B) Payment failure tracking (structured)

Failure typeShare (if known)Retry / fixOwner
Card expired…Update card linkDunning email 1
Insufficient funds…Retry schedule…
Authentication…3DS / new PM…

C) Retention email series — compensation psychology

Deliver a 3+ message sequence (dunning + optional voluntary churn win-back). Each message must include:

  • Subject line A/B
  • Body skeleton (short)
  • Compensation psychology label (e.g. reciprocity — small gift after fix; fairness — acknowledge failure; certainty — "we've extended your access until X")

Psychology angles to use (at least two across the series)

  • Fairness — acknowledge failed charge or bad experience without blame.
  • Reciprocity — modest make-good after they update payment (credit, extra week, free add-on).
  • Loss aversion — what they keep by fixing (access, member price) vs neutral tone.
  • Certainty — single clear CTA; "one click to update card."

Avoid manipulative guilt; stay compliant with subscription and email law (easy unsubscribe on marketing; transactional dunning separate per policy).

When NOT to use

  • Single order shipping email only.
  • Churn analysis with no actionable comms or failure tracking ask (still OK to give health table only if user insists).

Split with other skills

  • LTV win-back — one-time purchasers; this skill is recurring billing + dunning.
  • Payment funnel — one-time checkout; this skill is renewal attempts.

平台分布

OpenClaw

73.13%
按下载量换算1,611

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills