Token导航 LogoToken导航TokenDH.com
开发只读clawhub未标认证来源可访问clear审计提醒

ltv-loyalty-winbackLTV 忠诚赢回

Agent Skill

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

总安装

8,067

周安装

343

GitHub Stars

公开资料未说明

下载量

2,826
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:ltv-loyalty-winback(LTV 忠诚赢回)
来源仓库:https://github.com/rijoyai/ltv-loyalty-winback
安装命令:
openclaw skills install ltv-loyalty-winback
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install ltv-loyalty-winback

简介

根据购买和等级数据预测重复客户流失情况,然后通过 VIP 关怀或限时优惠触发特定于分支机构的赢回工作流程。

SKILL.md

name
ltv-loyalty-winback
description
Predict repeat-customer churn risk from purchase history and tier activity, then output branch-specific win-back and activation workflows. Use when 90-day (or similar) non-repurchase cohorts are growing, membership or tier engagement is dropping, points are about to expire and you need pre-expiry campaigns, RFM or LTV segmentation is discussed, or the user wants automated reactivation plays for lapsed buyers. Branch logic: high-value VIPs get white-glove CS care plans; standard buyers get time-bound discount or incentive bait. Also trigger on "silent customers," lapse risk, loyalty program fatigue, or win-back sequences — even if they only say "our repeat rate is falling." Do NOT use for simple single-order purchase confirmations, shipping notices, or one-off transactional messages with no retention or churn context.
compatibility
required
[]

LTV loyalty churn alert & win-back

You connect historical purchase frequency (and recency)silence / churn riskautomated activation workflows (journeys, messages, and ops hooks).

When NOT to use (should-not-trigger)

  • Single purchase confirmation only ("thanks for your order") with no retention ask.
  • Pure transactional templates with no lapse or segment context.

If the user later adds "many haven't bought again," switch to full workflow mode.

Gather context

  1. Recency: last purchase date distribution; spike in 90d+ silent (or merchant’s window).
  2. Frequency: orders per customer in last 12 months; baseline vs cohort.
  3. Monetary: AOV and cumulative spend — VIP threshold (define or ask).
  4. Tier / points: tier rules, points expiry date and notice rules.
  5. Channel: email, SMS, app push, CS outreach — constraints and consent.

For RFM-style cutoffs and workflow templates, read references/loyalty_playbook.md when needed.

Core workflow (always)

  1. Risk framing — Classify silence (e.g. at-risk: no order in 90d; high-risk: 120d+; formerly frequent now cold).
  2. Segment branch

- VIP / high-valueDedicated CS care (named contact, proactive outreach, perk without trashing margin — early access, bundle concierge, not only generic % off). - Standard buyerTime-bound discount or incentive bait (deadline, code, stack rules clear).

  1. Activation workflow — Trigger, wait steps, exit rules, measure (reactivation rate, incremental revenue).

Mandatory outputs (full engagement)

Every full churn / loyalty answer must include:

  1. Risk summary — Who is silent, how many (or %), vs historical norm.
  2. Two branches — At least one block labeled VIP / high-value (CS care) and one Standard (discount bait), even if one segment is empty ("if no VIPs, still document threshold").
  3. Win-back plan table — concrete steps + channel + timing.
  4. Points expiry branch (if applicable) — Pre-expiry nudge sequence before burn.

Win-back plan table (required shape)

SegmentSilence signalActionChannelTiming
VIPe.g. 90d + LTV top decileDedicated CS check-in + perkEmail + optional callDay 0, Day 7
Standarde.g. 90d no orderLimited-time offerEmail/SMSDay 0, Day 3, Day 10
Points at riskExpiry in 14dRedeem nudge + basket builderEmailT-14, T-7, T-2

Adjust rows to data; keep VIP vs Standard distinction explicit.

VIP branch (content requirements)

  • Named or role-based concierge line.
  • Non-price-first value where possible (early access, restock hold, bundle suggestion).
  • Escalation path if no response.

Standard branch (content requirements)

  • Time-bound offer (end date).
  • Clear code or auto-apply and exclusions.
  • Single primary CTA.

Success metrics (suggest in every full run)

  • Reactivation rate (ordered within 30d of campaign).
  • Incremental revenue vs holdout.
  • Unsubscribe / complaint rate (guardrail).

Split with other skills

  • Affiliate reconciliation → not this skill.
  • Abandoned checkout (session drop) → checkout skill; this skill is post-purchase lapse.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

76.59%
按下载量换算2,164

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills