RFM Segment Naming. Use when work requires definitions for segments such as loyal, high-potential, and due for reactivation; process the specified inputs using this method and verify the deliverable
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Mk 380?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/backtrue-mk-380)
---
name: mk-380
description: "RFM Segment Naming. Use when work requires definitions for segments such as loyal, high-potential, and due for reactivation; process the specified inputs using this method and verify the deliverable"
---
# MK-380 | RFM Segment Naming
For ordinary chat, upload `packs/mk-380.md`, which includes the shared rules, this method, and required references
## Purpose
This skill delivers: **Definitions for segments such as loyal, high-potential, and due for reactivation**
Do not rank RFM results from different observation periods as if they shared one basis; separately verify the purpose and authorization for any list export or use
## Required inputs
Raw inputs: verified R/F/M scores and three-digit codes, interval/window version, approved brand label map; the embedded course example retains unresolved source entries
## Method steps
1. Verify R/F/M concatenation and rule version. Approved brand mappings take precedence; adopting the course example requires a stated source and approved use, not an assumed universal brand policy
2. Match each code exactly. One unambiguous match yields a label; none is unmapped and multiple matches are conflicts. Do not infer dormancy from sums, nearest codes or all unlisted records
3. For the embedded source table, match explicit three-digit codes. Literal 511.423 and 1~ lack unambiguous definitions; retain them pending an approved expansion rather than split them or label every 1-prefix member
4. Deliver raw RFM, scores, code, matched row, label, map version and task. Course channel suggestions are candidates; actual contact follows eligibility and need, not the label alone
5. Recompute groups after interval, M, window or map changes; a map-only correction rematches the same verified code. New eligibility/needs revise actions instead of forcing the old-group offer
## Calculation and interpretation
Original course slide 33 example (literal code notation retained)
| Label | Literal Total Score notation | Source channel candidates |
|---|---|---|
| Loyal | 555,554,553,545,544,543,535,534,533 | EDM, SMS, LINE, community |
| Loyal to reactivate | 455,454,453,445,444,443,435,434,433,355,354,353,345,344,335,255,254,245,244 | EDM, SMS, LINE, community |
| High potential | 552,551,542,541,532,531,525,524,523,522,521,515,514,513,452,451,442,441,432,431,425,424,415,414, | EDM, SMS |
| Low potential | 512,511.423,422,421,413,412,411,352,351,343,342,341,334,333,332,331,325,324,323,322,321,315,314,313,312,311,253,252,251,243,242,241,235,234,233,232,231,225 | SMS for major occasions as candidates |
| Dormant | 224,223,222,221,215,214,213,212,211,1~ | SMS for major occasions as candidates |
The source does not unambiguously delimit 511.423 or define 1~. Leave 511, 423 and unlisted 1-prefix codes unresolved until an explicit approved map exists. Other unlisted codes are also unmapped
Hypothetical adoption of this table: 543 is Loyal; a revised R interval changes the same member to code 443, Loyal to reactivate. Code 511 remains unresolved rather than guessed Low potential; an approved brand map explicitly labeling it Low potential enables that label
Source: [Original course slide 33: member types and Total Score](https://docs.google.com/presentation/d/1ZYpstuVAXGk9KdZt1QZm2OQ7ozpYYtfrBf0Xsy7kRx8/edit#slide=id.g2b001449a48_0_208); candidate task objectives: [slide 34](https://docs.google.com/presentation/d/1ZYpstuVAXGk9KdZt1QZm2OQ7ozpYYtfrBf0Xsy7kRx8/edit#slide=id.g2b001449a48_0_213)
Decision rules authored by ThinkWithBlack on 2026-10-14; original course sources are retained below
## Required output fields
| Order | Field | How to fill it in |
|---:|---|---|
| 1 | Customer key | Original evidence, intermediate method results, or an explicit unknown; do not fabricate |
| 2 | Observation coverage | Original evidence, intermediate method results, or an explicit unknown; do not fabricate |
| 3 | Last valid purchase | Original evidence, intermediate method results, or an explicit unknown; do not fabricate |
| 4 | R | Original evidence, intermediate method results, or an explicit unknown; do not fabricate |
| 5 | F | Original evidence, intermediate method results, or an explicit unknown; do not fabricate |
| 6 | M | Original evidence, intermediate method results, or an explicit unknown; do not fabricate |
| 7 | Applied segmentation rules | Original evidence, intermediate method results, or an explicit unknown; do not fabricate |
| 8 | Segment | Original evidence, intermediate method results, or an explicit unknown; do not fabricate |
| 9 | Limitations | Original evidence, intermediate method results, or an explicit unknown; do not fabricate |
## Method sources
Original file: 營業額提升主要關鍵(二)社群/會員經營技巧
Source locator: RFM
Source basis: extracted from course materials
Original URL: https://docs.google.com/presentation/d/1ZYpstuVAXGk9KdZt1QZm2OQ7ozpYYtfrBf0Xsy7kRx8/edit
English translation of source excerpt retained in the master sheet:
> Use RFM rules for segmentation to turn new customers (one purchase) into returning customers (more than one purchase)