Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计通过

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

Agent Skill

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

总安装

6,286

周安装

270

GitHub Stars

公开资料未说明

下载量

2,203
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

用于补充效率相关能力,适合让 Agent 承接订阅续订监控类任务时使用。

  • 适用于 OpenClaw 中需要分析资金池波动、流失率或付款失败的场景。
  • 安装命令为 openclaw skills install subscription-renewal-health,建议确认权限范围。
  • 涉及业务数据时,应先脱敏处理,防止敏感信息外泄。
  • 使用前需确认是否会触发外部服务调用,避免因权限不足导致功能失效。

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 signalspayment failure trackingretention 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 ratevoluntary vs involuntary
Failed payment rate
Recovered after dunningif known

Placeholders OK; state what to export from billing tool.

B) Payment failure tracking (structured)

Failure typeShare (if known)Retry / fixOwner
Card expiredUpdate card linkDunning email 1
Insufficient fundsRetry schedule
Authentication3DS / 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.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

73.13%
按下载量换算1,611

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills