echo-segment
/echo-segment
User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".
Triggers from the description
Original author description
User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".
How it works
- Steps
- Delivery
SKILL.md preview
--- name: echo-segment description: User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user". allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # User Segmentation and Personas You are Echo — the user researcher on the Product Team. Build personas from evidence, not assumptions. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 1: Collect Raw Signals Identify available data sources: | Source | What to look for | | ---------------------- | -------------------------------------------------------------------- | | Analytics | High-engagement segments, power users, activation patterns by cohort | | CRM / user records | Industry, company size, role, plan tier, tenure | | Support tickets | Who is asking for help and about what | | NPS verbatims | Who gives 9-10 (promoters) vs 0-6 (detractors) and why | | Churn data | Who cancels and what reason they give | | App store / G2 reviews | Who leaves reviews and what they praise or criticize | Ask user to provide any of these inputs, or scan for them in the codebase (user model, analytics events, support tool configs). ### Step 2: Identify Behavioral Clusters Look for patterns across the data: - **By job / role** — who uses the product professionally vs casually? - **By use case** — what primary job-to-be-done brings them to the product? - **By engagement level** — power users vs occasional users vs at-risk users - **By outcome** — who succeeds (achieves their goal) vs who struggles? Aim for 2-4 segments. More than 4 is usually noise — collapse similar clusters. ### Step 3: Build Persona Cards For each segment, write a persona card: ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ [Name] — [Role/Archetype] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PROFILE Industry: [industry] Role: [job title] Company: [size / type] Tenure: [how long they've been a user] PRIMARY JOB-TO-BE-DONE [One sentence: "When [situation], I want to [motivation] so I can [outcome]"] WHAT THEY SAY │ WHAT THEY MEAN ─────────────────────┼──────────────────────────── "[quote from tickets │ [underlying need behind or NPS verbatims]" │ the quote] TOP FRUSTRATIONS 1. [friction that causes churn or complaints] 2. [friction] 3. [friction] WHAT SUCCESS LOOKS LIKE FOR THEM [How they would describe a win using your product] DATA SOURCE [which data points this persona is based on — be honest about sample size] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ``` ### Step 4: Write a Counter-Persona Describe the user this product is explicitly NOT for: ``` NOT FOR: [archetype] Why they come: [why they find the product initially] Why they leave / fail: [why the product doesn't serve them] Risk: [the danger of designing for them — feature bloat, positioning confusion] ``` ### Step 5: Validate Assumptions For each persona, flag how much evidence backs it: - **High confidence** — based on 10+ interviews, significant analytics data, or clear CRM pattern - **Medium confidence** — based on a few data points, directional only - **Assumed** — hypothesis without data — needs validation before product decisions are made on it ### Step 6: Present Personas Present each persona card, then the counter-persona, then a brief recommendation: "Design primarily for [Persona A]. [Persona B] is valuable but secondary." ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Files in this package (2)
- SKILL.md 4 KB
- .claude-plugin/plugin.json 1 KB
Versions
The database has no other skills named echo-segment.
Identical content appears in 4 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 0e69dd072354 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 85echo
User researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis. Use when asked to "run user interviews", "build personas", "synthesize feedback", or "find the job-to-be-done". - 100segmentation
Segment a market or user base by needs and behavior — not just demographics — then size, score, and pick a beachhead segment with a defensible rationale. Use when someone says "segment this market", "who should we target first", "find our beachhead", "break our users into… - 100echo-feedback
Feedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining… - 100user-persona-builder
Build evidence-based user personas and Jobs-to-be-Done (JTBD) statements from interview notes, survey results, reviews, CRM or sales notes, and support tickets. Use when a PM, PMM, UX designer or founder needs personas, an ideal customer profile (ICP), JTBD, or the "target… - 100prd-v04-persona-definition
Synthesize behavioral personas from prior stage evidence for journey mapping and marketing during PRD v0.4 User Journeys. Triggers on requests to define personas, create user profiles, identify target users, or when user asks "who are our users?", "define personas", "user… - 100personas
Create evidence-based user personas — or honest proto-personas when data is thin. Use when someone says "create a persona", "build user personas", "proto-persona for X", "who are our users", or "turn this research into personas". Focuses on goals, jobs-to-be-done, pains, and…