Token导航 LogoToken导航

Agent Skill · 研究检索

customer-retention-engine(客户保留引擎)

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

customer-retention-engine 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有未通过项,按安装量在研究检索类的 73,675 个 Skill 里排第 55,410。

总安装 480周安装 20GitHub Stars 19下载 160核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill customer-retention-engine

这个 Skill 是做什么的

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

客户保留引擎主动识别即将流失的高价值客户,实施个性化干预防止流失。适用于电商平台或 SaaS 产品,聚焦于预防性留存而非事后挽回已流失用户。基于购买频率下降、订单金额减少等行为信号建立预警机制。输出可执行的客户名单与推荐触达策略,集成 Klaviyo 等平台实现自动化工作流。

需接入订单与用户行为数据源以确保信号准确性,避免误判正常波动。

来源仓库内路径:skills/customer-retention-engine

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

customer-retention-engine 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill customer-rete…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

customer-retention-engine 支持哪些 AI 工具?

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

customer-retention-engine 需要什么权限?

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

customer-retention-engine 是免费的吗?

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

customer-retention-engine 用的人多吗?

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

customer-retention-engine 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
customer-retention-engine

客户保留引擎 · 本页

48019需要联网未明确未通过

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

SKILL.md 原文

Customer Retention Engine

Overview

Acquiring a new customer costs 5–7x more than retaining an existing one. A retention engine identifies customers who show declining engagement — reduced purchase frequency, decreasing order values, browsing without buying — and intervenes with personalized campaigns before they lapse. Klaviyo and AutomateWoo can build these workflows with no custom code using predictive analytics built into the platform.

Note: For reactivating already-lapsed customers, see @win-back-reactivation. This skill focuses on proactive churn prevention before customers lapse.

When to Use This Skill

  • When repeat purchase rate is declining month-over-month
  • When a significant percentage of customers only ever purchase once
  • When you want to proactively contact customers before they go fully dormant
  • When building a post-purchase nurture program beyond the first 30 days
  • When needing to identify which customers are worth offering a discount vs. which will repurchase anyway

Core Instructions

Step 1: Choose the right tool for your platform

PlatformRecommended ToolWhy
ShopifyKlaviyoKlaviyo's predictive analytics automatically calculates expected next purchase date and churn risk for every customer; no manual scoring needed
WooCommerceAutomateWoo ($99/yr)Deep WooCommerce integration, "Customer win-back" workflow type, RFM segmentation built in
BigCommerceKlaviyo or OmnisendBoth integrate natively with BigCommerce order events and offer predictive churn scoring
Custom / HeadlessKlaviyo (via API)Send order events to Klaviyo; use their predictive analytics to identify at-risk customers

Step 2: Define your churn threshold

Churn timing depends on your product's natural repurchase cycle:

Product CategoryExpected Repurchase CycleAt-Risk ThresholdChurned Threshold
Consumables (skincare, supplements)30–60 days60+ days since last order120+ days
Apparel/fashion60–90 days90+ days180+ days
Home goods90–180 days180+ days365+ days
Electronics accessories120–365 days180+ days365+ days

In Klaviyo, go to Analytics → Predictive Analytics to see Klaviyo's automatically calculated churn risk for your customer base. Klaviyo uses your actual order history to set these thresholds — no manual calculation needed.

Step 3: Build retention flows


Shopify with Klaviyo

Flow 1: Early warning — customers approaching their expected repurchase date

  1. Go to Klaviyo → Flows → Create Flow → Start from Scratch
  2. Set trigger: Metric → Expected Date of Next Order is in 7 days

- Klaviyo calculates this automatically using predictive analytics

  1. Add an email action with subject line: "Your favorites are waiting for you"

- Include: personalized product recommendations based on past purchases - Use the {{person.predicted_next_purchase_date}} variable to acknowledge timing

  1. Wait 3 days → Add a conditional: "Has placed an order since flow start?" → If No: send a follow-up email

Flow 2: High-value at-risk customers — personalized offer

  1. Create a new flow triggered by: Segment → "High-Value At-Risk" segment (configure segment below)
  2. Email: personalized exclusive offer (free shipping or 15% off for top-tier; no discount for mid-tier)
  3. Wait 5 days → If no purchase: SMS follow-up (for SMS-consented customers)

Create the "High-Value At-Risk" segment in Klaviyo:

  1. Go to Klaviyo → Segments → Create Segment
  2. Conditions:

- Predicted Churn Risk equals High OR Mid - AND Total Customer Value (Historic CLV) greater than $150 - AND Has not placed order in last 60 days

  1. Save as "High-Value At-Risk"

Flow 3: One-time buyer reminder

  1. Create a flow triggered by: Metric → Placed Order
  2. Wait 45 days
  3. Check: "Total number of orders equals 1" → If yes:
  4. Email: "Based on your [product name] purchase, you might love these..." with 3–4 complementary product recommendations
  5. Wait 14 days → If still only 1 order: send final email with 10% welcome-back discount

WooCommerce with AutomateWoo
  1. Go to AutomateWoo → Workflows → Add Workflow
  2. Set trigger: Customer → Win Back

- AutomateWoo has a built-in "Customer Win Back" trigger that fires at configurable intervals after last purchase

  1. Set timing rules:

- Workflow A: 45 days since last purchase — send personalized recommendations email - Workflow B: 75 days since last purchase — send exclusive offer email with discount

  1. Add a rule to each workflow: "Customer has not purchased since workflow was created" — auto-cancels on conversion
  2. For VIP customers: add a rule "Customer total spend > $500" to route to a separate workflow with better offers

AutomateWoo also includes built-in RFM segmentation — go to AutomateWoo → Reports → RFM Analysis to see your customer segments visually.


BigCommerce
  1. Install Klaviyo from the BigCommerce App Marketplace
  2. Klaviyo automatically syncs all BigCommerce order history
  3. Follow the same Klaviyo flow setup described in the Shopify section above
  4. BigCommerce order events trigger Klaviyo flows in real-time after the integration is connected

Custom / Headless

Send order events to Klaviyo's API to trigger retention flows:

// Send order event to Klaviyo when an order is completed
async function trackKlaviyoOrder(order: Order) {
  await fetch('https://a.klaviyo.com/api/events/', {
    method: 'POST',
    headers: {
      'Authorization': `Klaviyo-API-Key ${process.env.KLAVIYO_PRIVATE_KEY}`,
      'Content-Type': 'application/json',
      'revision': '2024-10-15',
    },
    body: JSON.stringify({
      data: {
        type: 'event',
        attributes: {
          metric: { data: { type: 'metric', attributes: { name: 'Placed Order' } } },
          profile: { data: { type: 'profile', attributes: { email: order.customerEmail } } },
          properties: {
            $value: order.subtotal,
            OrderId: order.id,
            Items: order.lineItems.map(i => ({ ProductName: i.name, ItemPrice: i.price })),
          },
        },
      },
    }),
  });
}

Klaviyo's predictive analytics then automatically calculates churn risk and expected next purchase date based on these events.

Step 4: Configure intervention timing and incentives

Match interventions to customer value tier:

Customer TierInterventionIncentive
VIP (6+ orders, $500+ LTV)Personalized email from "founder"No discount — just recognition and early access
High-value (3–5 orders)Email + SMS follow-upFree shipping (protects margin)
Standard (1–2 orders)Email sequence10% discount at final step only
One-time buyerEmail at 45 days10% off second order

Step 5: Measure retention lift

Track these in Klaviyo or AutomateWoo dashboards:

MetricTargetWhere to Find
Flow revenueGrowing month-over-monthKlaviyo → Flows → Analytics
Repeat purchase rate> 25% of customersShopify: Analytics → Customer cohorts. Klaviyo: Segment analytics
At-risk segment shrinkingDecrease vs. prior monthKlaviyo → Segments → Size history
Churn rateDecliningCompare lapsed customer count month-over-month

Best Practices

  • Never discount VIP customers reflexively — high-LTV customers who are slightly overdue may just be busy; a soft nudge without discount often works and protects margin
  • Personalize based on actual purchase history — Klaviyo's dynamic product blocks automatically show recommendations based on what the customer has bought
  • Set a contact frequency cap — in Klaviyo, use Smart Sending and set a daily message limit; at-risk customers should not receive more than one touchpoint per week
  • Use Klaviyo's predictive analytics — do not manually calculate churn scores; Klaviyo computes expected next purchase date and churn risk automatically from your order data
  • Close the loop with CS for high-value customers — for accounts over $1,000 LTV showing high churn risk, route to a customer success rep via Gorgias or Zendesk for personal outreach

Common Pitfalls

ProblemSolution
Sending retention emails to customers who just boughtAdd a flow filter in Klaviyo: "Has placed an order in last 7 days → skip"; AutomateWoo's "Customer has not purchased since workflow was created" rule handles this
Discounts eroding margin on customers who would have repurchased anywayUse Klaviyo's predictive analytics: only offer discounts when predicted churn risk is "High"; skip for "Mid" and "Low"
Single-purchase customers receiving win-back messaging too earlySet a minimum 45-day window before treating a one-time buyer as at-risk
Flows sending to unsubscribed contactsKlaviyo respects unsubscribes automatically; ensure your Shopify/WooCommerce unsubscribe events sync to Klaviyo in real-time

Related Skills

  • @lifecycle-marketing-automation
  • @win-back-reactivation
  • @loyalty-program-optimization
  • @email-marketing-automation
  • @email-list-segmentation

平台分布

Codex

34.81%
按下载量换算56

Claude

31.54%
按下载量换算50

Cursor

20.52%
按下载量换算33

Gemini CLI

10.48%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

未通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills