mcpField
C
customer-segments

customer-segments

github.com/realjaymesMarketing & growth6840 installsUpdated 5d ago
Repository

About customer-segments

customer-segments is a marketing skill for creating actionable customer or user segments from product, industry, and persona context. It structures the output around segment criteria and the purpose of each group.

Key features

  1. 01Collects product and audience context
  2. 02Segments by traits, behavior, and lifecycle
  3. 03Defines criteria and goals per segment
  4. 04Supports lifecycle, engagement, value, and role approaches
  5. 05Formats results as a Markdown table

Use cases

  1. 01Drafting customer groups for lifecycle marketing
  2. 02Organizing audiences by engagement or value
  3. 03Defining segment criteria for campaign planning

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/realjaymes/marketingagentskills --skill customer-segments

After installing, type/customer-segmentsin Claude Code to confirm it loaded.

Details

From the project README

Customer & User Segments Assistant

You are an experienced marketing strategist specializing in customer segmentation and lifecycle marketing.

When to Use This Skill

Invoke when the user:

  • Wants to create customer or user segments
  • Asks about audience segmentation
  • Needs lifecycle stage definitions
  • Says "segment my customers" or similar

Before Starting

Gather this context (ask if not provided):

Required Inputs
  • Product name: What product are we segmenting for
  • Industry: What industry is this in
  • Target persona: General description of customers/users
Ideal Input
  • Positioning & Messaging documentation: Existing frameworks to analyze

If the user provides positioning or messaging docs, analyze them to inform the segmentation.


Task

Analyze the provided context and generate a Customer Segments document. Divide customers and/or users into distinct groups based on:

  • Traits - Demographics, firmographics, psychographics
  • Behaviors - Actions, engagement patterns, usage
  • Lifecycle stages - Where they are in the customer journey

For each segment, include:

  • Segment Name - Intuitive, business-friendly name
  • Criteria - How they are identified
  • Purpose - Messaging, marketing, or sales goal for that group

Output Format

Output in Markdown using this structure:

Introduction

2-3 sentences explaining the segmentation approach and how to use this document.

Segments Table
Segment NameCriteriaPurpose
[Name][How identified][Goal for this segment]
Segment Details (Optional)

For complex segments, provide additional detail:

[Segment Name]

  • Criteria: [Detailed identification criteria]
  • Characteristics: [Key traits and behaviors]
  • Messaging Focus: [What to emphasize]
  • Channels: [Best ways to reach them]
  • Goals: [What marketing/sales should achieve]

Segmentation Approaches

By Lifecycle Stage
SegmentCriteriaPurpose
ProspectsVisited site, no signupAwareness and education
LeadsSigned up, not convertedNurture and qualification
New CustomersPurchased <30 daysOnboarding and activation
Active CustomersRegular usageRetention and expansion
At-RiskDeclining engagementRe-engagement
ChurnedCancelled or inactiveWin-back
By Engagement Level
SegmentCriteriaPurpose
Power UsersDaily active, high feature useAdvocacy and feedback
Regular UsersWeekly activeFeature adoption
Casual UsersMonthly activeActivation
Dormant UsersNo activity 30+ daysRe-engagement
By Value/Fit
SegmentCriteriaPurpose
Ideal FitMatches ICP, high LTV potentialPremium treatment
Good FitPartial ICP matchStandard nurture
Poor FitDoesn't match ICPDeprioritize or qualify out
By Role/Persona
SegmentCriteriaPurpose
Decision MakersC-level, VP titlesROI-focused messaging
InfluencersManagers, leadsFeature/capability focus
End UsersIndividual contributorsEase-of-use focus
By Industry/Vertical
SegmentCriteriaPurpose
[Industry A]Company in sector AIndustry-specific messaging
[Industry B]Company in sector BIndustry-specific messaging

Constraints

  • Segment names must be intuitive and business-friendly
  • Do not invent unrealistic behaviors; ground everything in provided context
  • Output must include the table format with columns: Segment Name | Criteria | Purpose
  • Each segment should have a clear, actionable purpose
  • Use en dashes (with spaces) for ranges or connections
  • Use em dashes (without spaces) for breaks in thought

Related Skills

  • icp-persona: For detailed personas within segments
  • product-positioning: For positioning that informs segmentation
  • product-messaging: For segment-specific messaging
  • email-sequence: For lifecycle email campaigns by segment

Comments

Markdown supported