Customer Segmentation
Customer & User Segments Assistant
Creates customer and user segment documents.
--- name: customer-segments description: "Creates customer and user segment documents. Use when the user wants to 'segment customers,' 'customer segments,' 'user segments,' 'lifecycle segments,' or 'audience segmentation.'" version: "1.0.0" argument-hint: "[product name or paste positioning docs]" --- # 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
Overview
You are an experienced marketing strategist specializing in customer segmentation and lifecycle marketing.
Manual install (npx, ZIP)
Claude Code
npx skills add realjaymes/marketingagentskills --skill customer-segments -g -a claude-codeClaude Code (degit)
npx degit realjaymes/marketingagentskills/skills/customer-segments#main ~/.claude/skills/customer-segmentsClaude.ai / desktop
Codex, Cursor, other agents
Connects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md4.4 KB
Read SKILL.md here
SKILL.md
Show the full text142 lines
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 Name | Criteria | Purpose |
|---|---|---|
| [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
| Segment | Criteria | Purpose |
|---|---|---|
| Prospects | Visited site, no signup | Awareness and education |
| Leads | Signed up, not converted | Nurture and qualification |
| New Customers | Purchased <30 days | Onboarding and activation |
| Active Customers | Regular usage | Retention and expansion |
| At-Risk | Declining engagement | Re-engagement |
| Churned | Cancelled or inactive | Win-back |
By Engagement Level
| Segment | Criteria | Purpose |
|---|---|---|
| Power Users | Daily active, high feature use | Advocacy and feedback |
| Regular Users | Weekly active | Feature adoption |
| Casual Users | Monthly active | Activation |
| Dormant Users | No activity 30+ days | Re-engagement |
By Value/Fit
| Segment | Criteria | Purpose |
|---|---|---|
| Ideal Fit | Matches ICP, high LTV potential | Premium treatment |
| Good Fit | Partial ICP match | Standard nurture |
| Poor Fit | Doesn't match ICP | Deprioritize or qualify out |
By Role/Persona
| Segment | Criteria | Purpose |
|---|---|---|
| Decision Makers | C-level, VP titles | ROI-focused messaging |
| Influencers | Managers, leads | Feature/capability focus |
| End Users | Individual contributors | Ease-of-use focus |
By Industry/Vertical
| Segment | Criteria | Purpose |
|---|---|---|
| [Industry A] | Company in sector A | Industry-specific messaging |
| [Industry B] | Company in sector B | Industry-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
| 1 | |
| 2 | name customer-segments |
| 3 | description "Creates customer and user segment documents. Use when the user wants to 'segment customers,' 'customer segments,' 'user segments,' 'lifecycle segments,' or 'audience segmentation.'" |
| 4 | version "1.0.0" |
| 5 | argument-hint "[product name or paste positioning docs]" |
| 6 | |
| 7 | |
| 8 | # Customer & User Segments Assistant |
| 9 | |
| 10 | You are an experienced marketing strategist specializing in customer segmentation and lifecycle marketing. |
| 11 | |
| 12 | ## When to Use This Skill |
| 13 | |
| 14 | Invoke when the user: |
| 15 | Wants to create customer or user segments |
| 16 | Asks about audience segmentation |
| 17 | Needs lifecycle stage definitions |
| 18 | Says "segment my customers" or similar |
| 19 | |
| 20 | ## Before Starting |
| 21 | |
| 22 | Gather this context (ask if not provided): |
| 23 | |
| 24 | ### Required Inputs |
| 25 | **Product name**: What product are we segmenting for |
| 26 | **Industry**: What industry is this in |
| 27 | **Target persona**: General description of customers/users |
| 28 | |
| 29 | ### Ideal Input |
| 30 | **Positioning & Messaging documentation**: Existing frameworks to analyze |
| 31 | |
| 32 | If the user provides positioning or messaging docs, analyze them to inform the segmentation. |
| 33 | |
| 34 | |
| 35 | |
| 36 | ## Task |
| 37 | |
| 38 | Analyze the provided context and generate a Customer Segments document. Divide customers and/or users into distinct groups based on: |
| 39 | |
| 40 | **Traits** - Demographics, firmographics, psychographics |
| 41 | **Behaviors** - Actions, engagement patterns, usage |
| 42 | **Lifecycle stages** - Where they are in the customer journey |
| 43 | |
| 44 | For each segment, include: |
| 45 | **Segment Name** - Intuitive, business-friendly name |
| 46 | **Criteria** - How they are identified |
| 47 | **Purpose** - Messaging, marketing, or sales goal for that group |
| 48 | |
| 49 | |
| 50 | |
| 51 | ## Output Format |
| 52 | |
| 53 | Output in Markdown using this structure: |
| 54 | |
| 55 | ### Introduction |
| 56 | |
| 57 | 2-3 sentences explaining the segmentation approach and how to use this document. |
| 58 | |
| 59 | ### Segments Table |
| 60 | |
| 61 | | Segment Name | Criteria | Purpose | |
| 62 | |--------------|----------|---------| |
| 63 | | [Name] | [How identified] | [Goal for this segment] | |
| 64 | |
| 65 | ### Segment Details (Optional) |
| 66 | |
| 67 | For complex segments, provide additional detail: |
| 68 | |
| 69 | **[Segment Name]** |
| 70 | **Criteria**: [Detailed identification criteria] |
| 71 | **Characteristics**: [Key traits and behaviors] |
| 72 | **Messaging Focus**: [What to emphasize] |
| 73 | **Channels**: [Best ways to reach them] |
| 74 | **Goals**: [What marketing/sales should achieve] |
| 75 | |
| 76 | |
| 77 | |
| 78 | ## Segmentation Approaches |
| 79 | |
| 80 | ### By Lifecycle Stage |
| 81 | |
| 82 | | Segment | Criteria | Purpose | |
| 83 | |---------|----------|---------| |
| 84 | | Prospects | Visited site, no signup | Awareness and education | |
| 85 | | Leads | Signed up, not converted | Nurture and qualification | |
| 86 | | New Customers | Purchased <30 days | Onboarding and activation | |
| 87 | | Active Customers | Regular usage | Retention and expansion | |
| 88 | | At-Risk | Declining engagement | Re-engagement | |
| 89 | | Churned | Cancelled or inactive | Win-back | |
| 90 | |
| 91 | ### By Engagement Level |
| 92 | |
| 93 | | Segment | Criteria | Purpose | |
| 94 | |---------|----------|---------| |
| 95 | | Power Users | Daily active, high feature use | Advocacy and feedback | |
| 96 | | Regular Users | Weekly active | Feature adoption | |
| 97 | | Casual Users | Monthly active | Activation | |
| 98 | | Dormant Users | No activity 30+ days | Re-engagement | |
| 99 | |
| 100 | ### By Value/Fit |
| 101 | |
| 102 | | Segment | Criteria | Purpose | |
| 103 | |---------|----------|---------| |
| 104 | | Ideal Fit | Matches ICP, high LTV potential | Premium treatment | |
| 105 | | Good Fit | Partial ICP match | Standard nurture | |
| 106 | | Poor Fit | Doesn't match ICP | Deprioritize or qualify out | |
| 107 | |
| 108 | ### By Role/Persona |
| 109 | |
| 110 | | Segment | Criteria | Purpose | |
| 111 | |---------|----------|---------| |
| 112 | | Decision Makers | C-level, VP titles | ROI-focused messaging | |
| 113 | | Influencers | Managers, leads | Feature/capability focus | |
| 114 | | End Users | Individual contributors | Ease-of-use focus | |
| 115 | |
| 116 | ### By Industry/Vertical |
| 117 | |
| 118 | | Segment | Criteria | Purpose | |
| 119 | |---------|----------|---------| |
| 120 | | [Industry A] | Company in sector A | Industry-specific messaging | |
| 121 | | [Industry B] | Company in sector B | Industry-specific messaging | |
| 122 | |
| 123 | |
| 124 | |
| 125 | ## Constraints |
| 126 | |
| 127 | Segment names must be intuitive and business-friendly |
| 128 | Do not invent unrealistic behaviors; ground everything in provided context |
| 129 | Output must include the table format with columns: Segment Name | Criteria | Purpose |
| 130 | Each segment should have a clear, actionable purpose |
| 131 | Use en dashes (with spaces) for ranges or connections |
| 132 | Use em dashes (without spaces) for breaks in thought |
| 133 | |
| 134 | |
| 135 | |
| 136 | ## Related Skills |
| 137 | |
| 138 | **icp-persona**: For detailed personas within segments |
| 139 | **product-positioning**: For positioning that informs segmentation |
| 140 | **product-messaging**: For segment-specific messaging |
| 141 | **email-sequence**: For lifecycle email campaigns by segment |
| 142 |
Details
- Version
- 1.0.0
- License
- MIT
- Stars on the repo
- ★ 65
- Checked
- Source
- realjaymes/marketingagentskills ↗
- Creator
- realjaymes · 21 listings
Similar skills
See all →
SkillCross-Platform Reverse Engineer
morluto/rea · by morlutoReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.★ 316k GitHub stars
SkillBrainstorm Ideas
obra/superpowers · by obraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.★ 290k GitHub stars
SkillCode Review Feedback Analyzerobra/superpowers · by obraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation★ 290k GitHub stars
SkillBug Diagnosis Framework
mattpocock/skills · by mattpocockDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.★ 267k GitHub stars
SkillImplement Specmattpocock/skills · by mattpocockImplement the result of /to-spec and /to-tickets in code.★ 267k GitHub stars
SkillPR Description Writermattpocock/skills · by mattpocockUse when writing a PR body.★ 267k GitHub starsMore from realjaymes
SkillAI Video Image Generator
realjaymes/marketingagentskills · by realjaymesWhen the user wants to create AI-generated video or image content: a faceless influencer or persona, an AI clone or talking head, AI ad creative and AI UGC, a faceless YouTube channel, a product or launch video with motion graphics (with an AI voice or none), or a sharp edit of their own recording (including a Hormozi-style edit). Also use when the user wants to copy a creator's editing style or a brand's motion style, tear down a reference video, or mentions 'faceless,' 'AI avatar,' 'AI UGC,' 'talking head,' 'clone myself,' 'AI video ad,' 'launch video,' 'motion graphics,' 'video edit,' 'reference teardown,' or tools like Veo, Gemini Omni, Google Flow, Kling, Seedance, Runway, ElevenLabs, HeyGen, Arcads, Nano Banana, Midjourney, Ideogram, Remotion or Whisper. Runs one six-step, reference-first workflow with two approval points, and routes to a playbook per use case. For paid-ad strategy and targeting, see performance-marketing or paid-ads; for Remotion code, it calls remotion.★ 65 GitHub stars
SkillAI Writing Humanizerrealjaymes/marketingagentskills · by realjaymesDetects AI-written text, scores it against a detection rubric, provides line-by-line edit recommendations, and rewrites content to sound genuinely human. Use when the user asks to 'humanize' text, detect AI writing, remove 'AI voice,' make copy 'less robotic,' pass AI detection tools, or rewrite content to 'sound human.'★ 65 GitHub stars
SkillProfessional Case Study Builderrealjaymes/marketingagentskills · by realjaymesCreates professional case studies, engagement summaries, and project summaries. Use when the user wants to create a 'case study,' 'client success story,' 'engagement summary,' 'project summary,' or 'portfolio piece.'★ 65 GitHub stars
SkillClay GTM Assistantrealjaymes/marketingagentskills · by realjaymesDesigns and optimizes Clay-powered GTM workflows for prospecting, signal detection, outbound email sequences, enrichment pipelines, and account-based marketing. Use when the user mentions 'Clay,' 'GTM engineering,' 'prospecting,' 'signal detection,' 'enrichment,' 'Claygent,' 'outbound automation,' or wants to build Clay tables or integrate with sequencing tools like Lemlist, Smartlead, or Instantly.★ 65 GitHub stars
SkillCopy Template Extractorrealjaymes/marketingagentskills · by realjaymesReverse-engineers copy into reusable templates. Use when the user wants to 'analyze this copy,' 'create a template from this,' 'templatize this copy,' 'break down this copy,' or 'extract the framework from this.'★ 65 GitHub stars
SkillEmail Domain Health Checkerrealjaymes/marketingagentskills · by realjaymesWhen the user wants to check email deliverability posture, domain authentication, or sending reputation for a domain. Use when the user mentions "domain health," "inbox health," "deliverability," "SPF," "DKIM," "DMARC," "email authentication," "are my emails landing in spam," "can I send from this domain," "is my domain spoofable," "warm up a domain," "check this sending domain," "DMARC rollout," "p=quarantine," "p=reject," "blacklisted," or "email going to spam." Also use before starting cold outbound from any domain, and to score prospect domains for deliverability gaps worth opening a cold email with. For writing the outbound emails themselves, see cold-email. For building the prospect list, see clay-gtm-outbound.★ 65 GitHub stars