Individual skill

segmentation-strategy

Builds a behavioral segmentation system for lifecycle messaging - RFM-based segments, event-driven membership triggers, one next action per segment, size audits, and send-time suppression rules. Use when someone asks "how should I segment my users", "our emails get ignored, who should get what", "how do I message at-risk users differently", or is personalizing lifecycle campaigns to cut unsubscribes and lift click-through. Do NOT use for building ad-platform audiences - use audience-targeting instead; for narrative customer personas use user-persona or icp-persona-builder; for mapping the full lifecycle stages and journeys use lifecycle-journey-map.

skills/segmentation-strategy/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Segmentation Strategy

Segmentation is the discipline of sending fewer, better messages to the right people. The goal is not many segments; it is segments that produce meaningfully different messages - because every segment that would receive the same email as its neighbor is pure operational cost, and a bloated segment map is why lifecycle programs stall at "monthly newsletter to everyone."

## Operating procedure

Follow in order: the behavioral axes (Step 2) must be chosen before segments are named (Step 3), and triggers (Step 4) cannot be written until each segment exists with a definition.

### Step 1: Gather inputs

Collect before designing; label estimates as guesses.

1. Product type: transactional (purchases) or engagement-based (sessions, actions). This decides whether the M in RFM is money or engagement depth.
2. The product events available in the messaging tool today - segments can only trigger on events that actually fire.