Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

ecom-rfm-analysisecom rfm 分析

Agent Skill

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

总安装

416

周安装

17

GitHub Stars

125

下载量

135
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:ecom-rfm-analysis(ecom rfm 分析)
来源仓库:https://github.com/asgard-ai-platform/skills
仓库路径:skills/ecom-rfm-analysis
安装命令:
npx skills add https://github.com/asgard-ai-platform/skills --skill ecom-rfm-analysis
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill ecom-rfm-analysis

简介

基于 Recency、Frequency、Monetary 三维度对客户进行行为细分,支持精准营销。

  • 适用于客户生命周期管理与复购激励策略设计,不依赖 demographic 假设。
  • 需使用实际交易数据划分 RFM 等级,输出 actionable 的客户分组建议。
  • 避免将不同年龄或性别客户混同处理,坚持“行为决定策略”原则。
  • ecom-rfm-analysis 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

RFM Analysis

Overview

RFM segments customers based on three behavioral dimensions: Recency (when they last bought), Frequency (how often they buy), and Monetary (how much they spend). It converts raw transaction data into actionable customer segments for targeted marketing.

Framework

IRON LAW: RFM Uses ACTUAL Behavior, Not Demographics

RFM is behavioral segmentation — it classifies by what customers DO,
not who they ARE. A 25-year-old and a 65-year-old in the same RFM segment
should receive the same treatment. Never mix RFM with demographic
assumptions.

The Three Dimensions

DimensionWhat It MeasuresHow to Calculate
Recency (R)Days since last purchaseToday - Last purchase date
Frequency (F)Number of purchases in periodCount of distinct transactions
Monetary (M)Total spend in periodSum of transaction values

Scoring Method (Quintile-Based)

  1. For each dimension, rank all customers and divide into 5 equal groups (quintiles)
  2. Score 5 (best) to 1 (worst): R=5 means most recent, F=5 means most frequent, M=5 means highest spend
  3. Combine into 3-digit RFM score (e.g., R5-F4-M5 = recent, frequent, high-value)

Note: For Recency, LOWER days = HIGHER score (more recent is better).

Key Segments

SegmentRFM PatternDescriptionStrategy
ChampionsR5, F5, M5Best customers, recent, frequent, high-valueReward, loyalty program, early access
LoyalR4-5, F4-5, M3-5Consistent buyersUpsell, cross-sell, referral program
Potential LoyalistsR4-5, F2-3, M2-3Recent, moderate frequencyNurture to increase frequency
At RiskR2-3, F3-5, M3-5Were frequent/high-value, not buying recentlyWin-back campaign, special offers
HibernatingR1-2, F1-2, M1-2Long dormant, low valueLow-cost reactivation or let go
New CustomersR5, F1, M1-2Just made first purchaseOnboarding, second-purchase incentive

Implementation Steps

Phase 1: Data Preparation

  • Required: Customer ID, Transaction Date, Transaction Amount
  • Clean: Remove refunds, test orders, internal orders
  • Set analysis window (typically 12-24 months)

Phase 2: Calculate RFM Scores

  • Calculate R, F, M for each customer
  • Assign quintile scores (1-5) for each dimension
  • Combine into segments

Phase 3: Segment and Act

  • Map each customer to a named segment (Champions, At Risk, etc.)
  • Design targeted actions per segment
  • Measure results: did targeted customers behave differently?

Output Format

# RFM Analysis: {Business}

## Data Summary
- Customers analyzed: {N}
- Analysis window: {start} to {end}
- Transactions: {N}

## Segment Distribution
| Segment | Count | % | Avg R (days) | Avg F | Avg M |
|---------|-------|---|-------------|-------|-------|
| Champions | {N} | {%} | {days} | {count} | ${X} |
| At Risk | {N} | {%} | ... | ... | ... |
| ... | ... | ... | ... | ... | ... |

## Key Findings
- Top 20% customers contribute {X%} of revenue
- {N} customers at risk of churning (were high-value, now dormant)
- {N} new customers need second-purchase nurturing

## Recommended Actions
| Segment | Action | Channel | Expected Impact |
|---------|--------|---------|----------------|
| Champions | {loyalty reward} | {email/app} | Increase AOV by X% |
| At Risk | {win-back offer} | {email/SMS} | Recover X% of dormant revenue |

Gotchas

  • RFM is backward-looking: It tells you what customers DID, not what they WILL do. Combine with predictive models (CLV prediction) for forward-looking insights.
  • Equal quintiles may not make sense: If 80% of customers bought only once, quintile 1-4 are all "one-time buyers." Consider custom breakpoints based on business context.
  • Monetary can be misleading for subscriptions: If everyone pays the same subscription fee, M dimension adds no information. Drop it and use RF only.
  • B2B vs B2C frequency differs: A B2B customer buying quarterly is "frequent." A B2C customer buying quarterly may be "at risk." Calibrate to business context.
  • Don't over-message At Risk customers: Bombarding dormant customers with emails can increase unsubscribes. One well-crafted win-back campaign is better than weekly emails.

Scripts

ScriptDescriptionUsage
scripts/rfm_score.pyScore customers on R/F/M and assign segment labelspython scripts/rfm_score.py --help

Run python scripts/rfm_score.py --verify to execute built-in sanity tests.

References

  • For Python/SQL implementation code, see references/rfm-implementation.md
  • For CLV prediction extending RFM, see references/clv-prediction.md

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.84%
按下载量换算50

Claude

29.83%
按下载量换算40

Cursor

20.82%
按下载量换算28

Gemini CLI

9.43%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills