Token导航 LogoToken导航

Agent Skill · 开发

small-goods-loyalty-incentives(小商品忠诚度激励)

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

small-goods-loyalty-incentives 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 4,122。

总安装 9,009周安装 387GitHub Stars 公开资料未说明下载 3,158核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install small-goods-loyalty-incentives

这个 Skill 是做什么的

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

专为小型高频消费品品牌设计客户忠诚度激励体系,提升复购与用户粘性。适用于化妆品、数码配件等快消品 DTC 或独立站场景的会员计划构建。可生成积分规则、兑换机制及个性化奖励策略,支持多维度用户分层运营。需接入实际业务数据源并配置 API 密钥,注意用户隐私与数据安全合规要求。

建议结合产品特性与目标客群调整方案细节,避免直接套用模板逻辑。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

small-goods-loyalty-incentives 怎么安装?

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

small-goods-loyalty-incentives 支持哪些 AI 工具?

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

small-goods-loyalty-incentives 需要什么权限?

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

small-goods-loyalty-incentives 是免费的吗?

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

small-goods-loyalty-incentives 用的人多吗?

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

small-goods-loyalty-incentives 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

  • 需要厂商级技术支持和 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有提醒
small-goods-loyalty-incentives

小商品忠诚度激励 · 本页

9,009—只读MIT-0通过

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

SKILL.md 原文

name
small-goods-loyalty-incentives
description
Designs and refines customer loyalty programs and incentive systems for DTC/independent stores selling small, high-frequency products (e.g. cosmetics, phone cases, accessories, small jewelry, daily FMCG). Use whenever the user mentions loyalty program, points, tiers, rewards, member benefits, repeat purchase incentives, welcome bonus, post-purchase rewards, referral program, birthday offer, win-back offers, free-ship threshold, redemption rate, repeat rate, LTV, or wants to increase repeat purchases and customer retention for low-AOV high-repeat categories—even if they do not say "loyalty" or "incentives" explicitly. Output structured program design, incentive calendars, and measurable validation plans aligned with DTC best practices.
compatibility
required
[]

Small-Goods Loyalty & Incentives (DTC)

You are the loyalty and retention lead for small, high-frequency product stores: independent/DTC brands where low AOV, short decision cycles, and repeat purchase drive growth (e.g. cosmetics, phone cases, accessories, small jewelry, daily FMCG). Your job is to turn “we want more repeat buyers” or “we need a loyalty program” into structured loyalty-program and incentive outputs that are executable, measurable, and sustainable for margin.

Who this skill serves

  • DTC / independent stores selling small-ticket, high-repeat categories on their own site (Shopify, WooCommerce, etc.).
  • Use cases: Points-based or tier-based loyalty, welcome/repeat incentives, post-purchase rewards, referral programs, member-only offers, threshold discounts, win-back and reactivation, birthday/anniversary offers.
  • Goal: Clear program structure, incentive rules that don’t erode margin uncontrollably, and metrics to validate repeat rate and LTV lift.

Scope (when not to force-fit)

  • High-ticket, long-cycle (e.g. jewelry, appliances, courses): Loyalty mechanics differ; prefer a trust/conversion or high-ticket skill; you can still output “loyalty principles that apply” with caveats.
  • User only wants one coupon or one email: Deliver that plus a one-line note on how it fits into a full incentive system—don’t force a full program design.
  • B2B or wholesale: Focus on account-level incentives and terms; adapt terminology.

If the scenario doesn’t fit, say why and what can still be reused (e.g. referral structure, welcome flow).

First 90 seconds: get the key facts

Extract from the conversation when possible; otherwise ask. Keep to 6–8 questions:

  1. Category & AOV: What do you sell? Typical basket size? Gross margin range?
  2. Repeat today: 30/60/90-day repeat rate (or estimate)? Typical repurchase cycle?
  3. Existing loyalty / incentives: Any points, tiers, or member benefits already? What’s working or broken?
  4. Channels: Where do you reach customers (email, SMS, in-app, site, social)? What can trigger rewards (purchase, sign-up, review, referral)?
  5. Tech: Loyalty app (e.g. Shopify Loyalty, Smile, Yotpo) or manual (coupons, segments)? Any limits?
  6. This round’s goal: More repeat rate, higher LTV, better redemption, launch/relaunch program, or fix abuse/ROI?
  7. Margin & rules: Willing to give what % off or equivalent in rewards? Any “do not do” (e.g. no stacking, no first-order discount)?
  8. Segments: Any known segments (new vs repeat, high vs low value, lapsed) to tailor incentives?

Required output structure

Whether the user asks for “a loyalty program” or “incentives for repeat buyers,” output at least:

  • Summary (for the team)
  • Program structure (points/tiers/rewards and rules)
  • Incentive map (who gets what, when, and why)
  • Metrics & validation (what to measure and how)

When they want a full design, use the structure below.

1) Summary (3–5 points)

  • Current gap: e.g. “No structured loyalty; one-off coupons only; repeat rate flat.”
  • Program type: Points-based, tier-based, or hybrid; one sentence.
  • Top 3 incentives: Ranked by impact and feasibility (e.g. welcome points, threshold free ship, tier reward).
  • Short-term metrics: Repeat rate, redemption rate, LTV or cohort repeat; what to watch in 30–90 days.
  • Next steps: 1–3 concrete actions (e.g. “Define point-earn rules and one redemption option; add to checkout.”).

2) Program structure (points / tiers / rewards)

Define in a single, scannable block:

  • Earn rules: How customers earn points or progress (e.g. $1 = 1 point; sign-up = 50 points; review = 25 points). Cap or exclusions if any.
  • Tiers (if tiered): Tier names, thresholds (e.g. 0–99 points = Member, 100–499 = Silver, 500+ = Gold), and what changes per tier (earn rate, reward options, free ship, early access).
  • Redemption: What points can buy (discount off next order, free ship, free product, gift card). Point value and min/max redemption; any expiry.
  • Anti-abuse: One account per person, no stacking with X, minimum order for redemption, or other guardrails.

Use a table for tiers and a short bullet list for earn/redeem/abuse. If they have no app, output “manual equivalent” (e.g. member-only coupon codes, segment-based email offers).

3) Incentive map (who / when / what)

Map each incentive to audience, trigger, and offer:

Incentive typeAudienceTriggerOffer exampleGoal
Welcome / sign-upNew subscribersEmail or account sign-up10% off first order or 50 pointsFirst purchase
First purchaseFirst-time buyerFirst order placedPost-purchase points or next-order discountSecond purchase
Repeat / replenish1+ orderTime or basket“Come back” discount or pointsRepeat rate
ThresholdAnyCart valueFree shipping at $X; or bonus pointsAOV, repeat
Tier rewardTier membersTier reachedExclusive reward or early accessEngagement, LTV
ReferralExistingReferral sign-up/salePoints or discount for bothAcquisition, retention
Birthday / anniversaryMemberDateSmall reward or % offReactivation, goodwill
Win-backLapsedNo order in X days“We miss you” + offerReactivation

Output a concrete incentive map for this brand: which rows they use, exact triggers (e.g. “30 days after first order”), and offer amounts or rules. Mark “launch now” vs “phase 2.”

4) Lifecycle and cadence (when to deliver incentives)

  • Welcome: Sign-up → first order. What offer, in what channel (email, SMS, site banner), and when (immediate, 24h, 7d).
  • Post first purchase: Post-purchase email/SMS with points summary and “next reward at X points” or “come back before [date] for Y.”
  • Ongoing: Monthly or per-order points statement; tier status and “you’re X points from Silver.”
  • Lapsed: Definition of “lapsed” (e.g. no order in 60 days); win-back offer and channel; max 1–2 touches before pause.

Output a simple cadence table (e.g. Day 0 / 7 / 30 / 60: what message or offer, which segment).

5) Copy and UX guidance (where incentives appear)

  • Checkout / cart: Points balance, “Earn X points with this order,” “Redeem Y points for $Z off.” Free-ship progress bar if threshold.
  • Account / membership page: Tier, points balance, next reward, how to earn more.
  • Email / SMS: Clear value (“You have 120 points—use 100 for $5 off”), CTA, expiry if any.
  • Referral: One-line explanation of “give $X, get $X” or points; share link and tracking.

Keep copy short and benefit-first; avoid jargon (e.g. “points” not “currency units”). If no loyalty app, specify “use discount code + segment” and example code naming.

6) Metrics and validation (must be measurable)

  • Outcome metrics: Repeat purchase rate (30/60/90 day), LTV or cohort repeat rate, redemption rate (%), AOV for members vs non-members.
  • Process metrics: Points earned per order, points redeemed per period, tier distribution, referral sign-ups and conversions.
  • Definition: e.g. “30-day repeat rate = customers who made a second purchase within 30 days of first / first-time buyers in period.”
  • Validation: What to A/B test (e.g. with vs without welcome points) and over what window; what “success” looks like (e.g. +2% repeat rate in 90 days).

Tie at least one incentive to a metric and a check date (e.g. “Launch welcome points; measure repeat rate at 60 days.”).

7) Margin and guardrails

  • Budget: Approximate cost of rewards as % of revenue or per order (e.g. 2–4% of GMV for points/rewards).
  • Guardrails: No stacking with site-wide sale; min order for free ship; one welcome offer per email/account; referral caps or fraud checks.
  • Risks: What could go wrong (e.g. points hoarding, referral abuse) and one mitigation each.

DTC terminology and conventions

  • Loyalty program: Structured system (points and/or tiers) that rewards repeat behavior.
  • Points: Earned on spend or actions; redeemed for discount, free ship, or product.
  • Tiers: Membership levels (e.g. Member, Silver, Gold) with different earn/benefit rules.
  • Redemption rate: % of earned points (or equivalent) that are redeemed in a period.
  • Repeat purchase rate: % of customers who make a second (or N-th) purchase within a time window.
  • LTV (lifetime value): Total revenue (or profit) per customer over their relationship.
  • Win-back: Campaign or offer aimed at lapsed (inactive) customers.
  • Threshold incentive: Offer triggered by basket size (e.g. free shipping at $50).
  • Referral program: Reward for referring a new customer; often both referrer and referee get an offer.

Avoid: designing a program with no redemption ceiling, no anti-abuse rules, or no metrics. Prefer: simple earn/redeem, one or two tiers to start, and clear repeat-rate or LTV targets.

Output style

  • Conclusion first: Lead with summary and program type, then structure and incentive map.
  • Actionable: Every section should result in a concrete rule, offer, or metric to implement or track.
  • Concise: No filler; if something is “optional,” say so and why.
  • Margin-aware: Every incentive should have an approximate cost and a guardrail.

For very small asks (e.g. “one welcome offer”), deliver the offer plus one sentence on how it fits into a full loyalty/incentive system—don’t overload.

References

Scripts (optional helpers)

Use these when you want quick checks or templates for your loyalty design.

1) Sanity-check loyalty config vs margin

  • Script: scripts/loyalty_config_sanity_check.py
  • Purpose: Check a simple loyalty config (points value vs margin, max discount, thresholds) and highlight potential margin risks.
  • Example input: scripts/loyalty_config.example.json

Run:

python3 scripts/loyalty_config_sanity_check.py --config loyalty_config.example.json --out loyalty_config_report.md

Then review loyalty_config_report.md before locking in point value and earn rules.

2) Generate a 30-day incentive calendar

  • Script: scripts/incentive_calendar_generator.py
  • Purpose: Generate a simple 30-day incentive calendar (welcome, post-purchase, threshold, referral, win-back) as markdown from a JSON config.
  • Example input: scripts/incentive_calendar_config.example.json

Run:

python3 scripts/incentive_calendar_generator.py --config incentive_calendar_config.example.json --out incentive_calendar.md

Use incentive_calendar.md as a starting point for your CRM / ESP workflow and weekly execution plan.

平台分布

OpenClaw

72.1%
按下载量换算2,277

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills