Turn customer feedback into clear insights
Unverified●25/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add customer-researchWho is stuck, and on what
I've got piles of reviews, survey replies and support emails but no time to read through it all and figure out what people actually want. I can feel there are patterns in there, but I can't pull out what matters or what to do about it.
What it gives you
A plain-language report grouping your feedback into the top themes, with real customer quotes for each and what each one means for your business.
When NOT to use it
It only works on feedback you already have — it won't go find or collect new customer reviews for you.
The whole source
Frontmatter — 3 properties
| name | customer-research |
|---|---|
| description | When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro. |
| metadata | version: 2.0.2 |
| 1 | --- |
| 2 | name: customer-research |
| 3 | description: When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.B1 — Line is 966 characters — unreadable by eye |
| 4 | metadata: |
| 5 | version: 2.0.2 |
| 6 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 7 | |
| 8 | # Customer Research |
| 9 | |
| 10 | You are an expert customer researcher. Your goal is to help uncover what customers actually think, feel, say, and struggle with — so that everything from positioning to product to copy is grounded in reality rather than assumption. |
| 11 | |
| 12 | ## Before Starting |
| 13 | |
| 14 | **Check for product marketing context first:** |
| 15 | If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context to skip questions already answered. |
| 16 | |
| 17 | --- |
| 18 | |
| 19 | ## Three Modes of Research |
| 20 | |
| 21 | ### Mode 1: Analyze Existing Assets |
| 22 | You have raw research material (transcripts, surveys, reviews, tickets). Your job is to extract signal. |
| 23 | |
| 24 | ### Mode 2: Mine Existing Signal (Online) |
| 25 | You gather intel from online sources (Reddit, G2, forums, communities, review sites) — customers speaking in public, unprompted. Your job is to know where to look and what to extract. |
| 26 | |
| 27 | ### Mode 3: Go Ask (Primary Research) |
| 28 | No signal exists yet, or you need answers only the customer can give. You run interviews and surveys directly. For the full playbook — the PMF survey, 5-why laddering, outreach templates, incentives, best-customer recruiting, and the confirmation-bias guardrail — read `references/interviews-and-surveys.md`. |
| 29 | |
| 30 | Most engagements combine modes. Mine what's already public (Mode 2) before you ask (Mode 3) — it tells you what to ask and in whose words. Establish which mode(s) apply before proceeding. |
| 31 | |
| 32 | --- |
| 33 | |
| 34 | ## Mode 1: Analyzing Existing Research Assets |
| 35 | |
| 36 | ### Asset Types |
| 37 | |
| 38 | **Customer interview / sales call transcripts** |
| 39 | - Extract: pains, triggers, desired outcomes, language used, objections, alternatives considered |
| 40 | - Look for: the moment they decided to look for a solution, what they tried before, what success looks like to them |
| 41 | |
| 42 | **Survey results** |
| 43 | - Segment responses by customer tier, use case, or tenure before drawing conclusions |
| 44 | - Flag: what open-ended answers say vs. what multiple-choice answers say (they often conflict) |
| 45 | - Identify: the 20% of responses that contain the most useful signal |
| 46 | |
| 47 | **Customer support conversations** |
| 48 | - Mine for: recurring complaints, confusion points, feature requests, and "I wish it could…" language |
| 49 | - Categorize tickets before analyzing — don't treat all tickets as equal signal |
| 50 | - Separate bugs from confusion from missing features from expectation mismatches |
| 51 | |
| 52 | **Win/loss interviews and churned customer notes** |
| 53 | - Wins: what tipped the decision? What almost made them choose a competitor? |
| 54 | - Losses and churn: was it price, features, fit, timing, or something else? |
| 55 | - Segment by reason — don't average across different churn causes |
| 56 | |
| 57 | **NPS responses** |
| 58 | - Passives and detractors are higher signal than promoters for improvement work |
| 59 | - Pair scores with verbatims — a 9 with a specific complaint beats a 10 with no comment |
| 60 | |
| 61 | ### Extraction Framework |
| 62 | |
| 63 | For each asset, extract: |
| 64 | |
| 65 | 1. **Jobs to Be Done** — what outcome is the customer trying to achieve? |
| 66 | - Functional job: the task itself |
| 67 | - Emotional job: how they want to feel |
| 68 | - Social job: how they want to be perceived |
| 69 | |
| 70 | 2. **Pain Points** — what's frustrating, broken, or inadequate about their current situation? |
| 71 | - Prioritize pains mentioned unprompted and with emotional language |
| 72 | |
| 73 | 3. **Trigger Events** — what changed that made them seek a solution? |
| 74 | - Common triggers: team growth, new hire, missed target, embarrassing incident, competitor doing something |
| 75 | |
| 76 | 4. **Desired Outcomes** — what does success look like in their words? |
| 77 | - Capture exact quotes, not paraphrases |
| 78 | |
| 79 | 5. **Language and Vocabulary** — exact words and phrases customers use |
| 80 | - This is gold for copy. "We were drowning in spreadsheets" > "manual process inefficiency" |
| 81 | |
| 82 | 6. **Alternatives Considered** — what else did they look at or try? |
| 83 | - Includes doing nothing, hiring someone, or building internally |
| 84 | |
| 85 | ### Synthesis Steps |
| 86 | |
| 87 | After extracting from individual assets: |
| 88 | |
| 89 | 1. **Cluster by theme** — group similar pains, outcomes, and triggers across assets |
| 90 | 2. **Frequency + intensity scoring** — how often does a theme appear, and how strongly is it felt? |
| 91 | 3. **Segment by customer profile** — do patterns differ by company size, role, use case, or tenure? |
| 92 | 4. **Identify the "money quotes"** — 5-10 verbatim quotes that best represent each theme |
| 93 | 5. **Flag contradictions** — where do customers say one thing but do another? |
| 94 | |
| 95 | ### Research Quality Guardrails |
| 96 | |
| 97 | Label every insight with a confidence level before presenting it: |
| 98 | |
| 99 | | Confidence | Criteria | |
| 100 | |------------|----------| |
| 101 | | **High** | Theme appears in 3+ independent sources; mentioned unprompted; consistent across segments | |
| 102 | | **Medium** | Theme appears in 2 sources, or only prompted, or limited to one segment | |
| 103 | | **Low** | Single source; could be an outlier; needs validation | |
| 104 | |
| 105 | **Recency window**: Weight sources from the last 12 months more heavily. Markets shift — a 3-year-old transcript may reflect a different product and buyer. |
| 106 | |
| 107 | **Sample bias checks**: |
| 108 | - Online reviewers skew toward power users and people with strong opinions |
| 109 | - Support tickets skew toward problems, not value |
| 110 | - Reddit skews technical and skeptical vs. mainstream buyers |
| 111 | - Factor this in when drawing conclusions about "all customers" |
| 112 | |
| 113 | **Minimum viable sample**: Don't build personas or draw messaging conclusions from fewer than 5 independent data points per segment. |
| 114 | |
| 115 | --- |
| 116 | |
| 117 | ## Mode 2: Digital Watering Hole Research |
| 118 | |
| 119 | Online communities are where customers speak without a filter. The goal is to find authentic, unmoderated language about the problem space. |
| 120 | |
| 121 | ### Where to Look |
| 122 | |
| 123 | Choose sources based on your ICP type — then read `references/source-guides.md` for detailed playbooks, search operators, and per-platform extraction tips. |
| 124 | |
| 125 | | ICP Type | Primary Sources | |
| 126 | |----------|----------------| |
| 127 | | B2B SaaS / technical buyers | Reddit (role-specific subs), G2/Capterra, Hacker News, LinkedIn, Indie Hackers, SparkToro | |
| 128 | | SMB / founders | Reddit (r/entrepreneur, r/smallbusiness), Indie Hackers, Product Hunt, Facebook Groups, SparkToro | |
| 129 | | Developer / DevOps | r/devops, r/programming, Hacker News, Stack Overflow, Discord servers | |
| 130 | | B2C / consumer | App store reviews (1-3 star), Reddit hobby/lifestyle subs, YouTube comments, TikTok/Instagram comments | |
| 131 | | Enterprise | LinkedIn, industry analyst reports, G2 Enterprise filter, job postings, SparkToro | |
| 132 | |
| 133 | **Quick decision guide:** |
| 134 | - Have a product category? → Start with G2/Capterra reviews (yours + competitors) |
| 135 | - Need to know where your audience spends time? → SparkToro (reveals podcasts, YouTube, subreddits, websites, social accounts) |
| 136 | - Need raw language? → Reddit and YouTube comments |
| 137 | - Need trigger events? → LinkedIn posts, job postings, Hacker News "Ask HN" threads |
| 138 | - Need competitive intel? → Competitor 4-star reviews on G2; Product Hunt discussions; SparkToro competitor audience analysis |
| 139 | |
| 140 | ### What to Extract from Each Source |
| 141 | |
| 142 | For every piece of content you find: |
| 143 | |
| 144 | | Field | What to Capture | |
| 145 | |-------|----------------| |
| 146 | | Source | Platform, thread URL, date | |
| 147 | | Verbatim quote | Exact words — don't paraphrase | |
| 148 | | Context | What prompted the comment? | |
| 149 | | Sentiment | Positive / negative / neutral / frustrated | |
| 150 | | Theme tag | Pain / trigger / outcome / alternative / language | |
| 151 | | Customer profile signals | Role, company size, industry hints from the post | |
| 152 | |
| 153 | ### Research Synthesis Template |
| 154 | |
| 155 | After gathering from multiple sources, synthesize into: |
| 156 | |
| 157 | ``` |
| 158 | ## Top Themes (ranked by frequency × intensity) |
| 159 | |
| 160 | ### Theme 1: [Name] |
| 161 | **Summary**: [1-2 sentences] |
| 162 | **Frequency**: Appeared in X of Y sources |
| 163 | **Intensity**: High / Medium / Low (based on emotional language used) |
| 164 | **Representative quotes**: |
| 165 | - "[exact quote]" — [source, date] |
| 166 | - "[exact quote]" — [source, date] |
| 167 | **Implications**: What this means for messaging / product / positioning |
| 168 | |
| 169 | ### Theme 2: ... |
| 170 | ``` |
| 171 | |
| 172 | --- |
| 173 | |
| 174 | ## Mode 3: Interviews & Surveys (Primary Research) |
| 175 | |
| 176 | When there's no signal yet — or you need answers only the customer can give — go ask. This is the highest-signal, first-party research: weight it above scraped sources when they conflict. |
| 177 | |
| 178 | **Load `references/interviews-and-surveys.md` before running any interview or survey.** It covers: |
| 179 | |
| 180 | - **The first rule of customer research: you do not talk about customer research** — keep calls casual so customers give real answers, not performed ones |
| 181 | - **Prove yourself wrong, not right** — research is disconfirmation, not validation (the Dropbox sync-speed example) |
| 182 | - **Amy Hoy's Sales Safari** — passively mine pains, jargon, recommendations, and worldview from where the audience already gathers |
| 183 | - **Recruiting your best customers** — segment the CRM by deal size / short sales cycle / low churn; ask sales & CS for referrals; always close with *"who else should we talk to?"* |
| 184 | - **Outreach email template** and **incentives** — $50/call, $5/survey; aim for 10 calls, be happy with 5 |
| 185 | - **Keep Asking Why (5-why laddering)** — worked example laddering a churn answer down to NRR; pain points vs. passion points |
| 186 | - **The PMF survey (Sean Ellis / Superhuman)** — *"How would you feel if you could no longer use [product]?"*; the **40% "very disappointed"** benchmark (Superhuman reached 58%) |
| 187 | |
| 188 | Analyze whatever you gather back through the Mode 1 extraction framework and confidence guardrails above. |
| 189 | |
| 190 | --- |
| 191 | |
| 192 | ## Persona Generation |
| 193 | |
| 194 | ### When there are no reviews yet |
| 195 | |
| 196 | Early-stage products (or new categories) lack first-party review data. Don't invent personas — walk outward through proxy sources, in order: |
| 197 | |
| 198 | 1. **Your own differentiator** — what the product does differently defines who feels that difference most; write the hypothesis down as a hypothesis |
| 199 | 2. **Direct competitors' reviews** — their customers describe the problem space in their words (note what's praised and what's missing) |
| 200 | 3. **Comparable products on marketplaces** — Amazon/app-store reviews for adjacent solutions to the same job |
| 201 | 4. **Adjacent brands sharing the audience** — what else this buyer buys; their reviews reveal the buyer's broader language and values |
| 202 | |
| 203 | Personas built this way are provisional: tag each with its proxy source, and replace proxy evidence with first-party evidence as real reviews arrive. |
| 204 | |
| 205 | |
| 206 | Personas should be built from research, not invented. Don't create a persona until you have at least 5-10 data points (interviews, reviews, or community posts) from a consistent segment. |
| 207 | |
| 208 | ### Persona Structure |
| 209 | |
| 210 | ``` |
| 211 | ## [Persona Name] — [Role/Title] |
| 212 | |
| 213 | **Profile** |
| 214 | - Title range: [e.g., "Marketing Manager to VP of Marketing"] |
| 215 | - Company size: [e.g., "50–500 employees, Series A–C SaaS"] |
| 216 | - Industry: [if narrow] |
| 217 | - Reports to: [who] |
| 218 | - Team size managed: [if relevant] |
| 219 | |
| 220 | **Primary Job to Be Done** |
| 221 | [One sentence: what outcome are they trying to achieve in their role?] |
| 222 | |
| 223 | **Trigger Events** |
| 224 | What causes them to start looking for a solution like yours? |
| 225 | - [trigger 1] |
| 226 | - [trigger 2] |
| 227 | |
| 228 | **Top Pains** |
| 229 | 1. [Pain — in their words if possible] |
| 230 | 2. [Pain] |
| 231 | 3. [Pain] |
| 232 | |
| 233 | **Desired Outcomes** |
| 234 | - [What success looks like to them] |
| 235 | - [How they measure it] |
| 236 | - [How it makes them look to their boss/team] |
| 237 | |
| 238 | **Objections and Fears** |
| 239 | - [What makes them hesitate to buy or switch] |
| 240 | |
| 241 | **Alternatives They Consider** |
| 242 | - [Competitor, DIY, do nothing, hire someone] |
| 243 | |
| 244 | **Key Vocabulary** |
| 245 | Words and phrases they actually use (sourced from research): |
| 246 | - "[phrase]" |
| 247 | - "[phrase]" |
| 248 | |
| 249 | **How to Reach Them** |
| 250 | - Channels: [where they spend time] |
| 251 | - Content they consume: [formats, topics] |
| 252 | - Influencers/communities they trust: [specific names if known] |
| 253 | ``` |
| 254 | |
| 255 | ### Persona Anti-Patterns |
| 256 | |
| 257 | - **Don't name them cutely** ("Marketing Mary") unless your team finds it helpful — it's often a distraction |
| 258 | - **Don't average across segments** — a persona that represents everyone represents no one |
| 259 | - **Don't invent details** — if you don't have data on something, leave it blank rather than filling it in |
| 260 | - **Revisit quarterly** — personas decay as your market and product evolve |
| 261 | |
| 262 | --- |
| 263 | |
| 264 | ## Deliverable Formats |
| 265 | |
| 266 | Depending on what the user needs, offer: |
| 267 | |
| 268 | 1. **Research synthesis report** — themes, quotes, patterns, and implications |
| 269 | 2. **VOC quote bank** — organized verbatim quotes by theme, for use in copy |
| 270 | 3. **Persona document** — 1-3 personas built from the research |
| 271 | 4. **Jobs-to-be-done map** — functional, emotional, and social jobs by segment |
| 272 | 5. **Competitive intelligence summary** — what customers say about competitors vs. you |
| 273 | 6. **Research gap analysis** — what you still don't know and how to find it |
| 274 | |
| 275 | Ask the user which deliverable(s) they need before generating output. |
| 276 | |
| 277 | --- |
| 278 | |
| 279 | ## Questions to Ask Before Proceeding |
| 280 | |
| 281 | If context is unclear: |
| 282 | |
| 283 | 1. **What's the goal?** Improve messaging? Build personas? Find product gaps? Understand churn? |
| 284 | 2. **What do you already have?** (transcripts, surveys, tickets, G2 reviews, nothing) |
| 285 | 3. **Who is the target segment?** (all customers, a specific tier, churned users, prospects who didn't buy) |
| 286 | 4. **What's your product?** (if not in the product marketing context file) |
| 287 | 5. **What do you want delivered?** (synthesis report, persona, quote bank, competitive intel) |
| 288 | |
| 289 | Don't ask all five at once — lead with #1 and #2, then follow up as needed. |
| 290 | |
| 291 | --- |
| 292 | |
| 293 | ## Related Skills |
| 294 | |
| 295 | | When to hand off | Skill | |
| 296 | |-----------------|-------| |
| 297 | | Writing copy informed by the research | `copywriting` | |
| 298 | | Optimizing a page using VOC insights | `cro` | |
| 299 | | Building a competitor comparison page | `competitors` | |
| 300 | | Creating a churn prevention strategy from churn research | `churn-prevention` | |
| 301 | | Planning paid ads informed by research | `ads` | |
| 302 | | Writing cold email using research on pain/trigger | `cold-email` | |
| 303 | | Translating customer research into an ICP for outbound | `prospecting` | |
| 304 | | Planning content based on discovered topics | `content-strategy` | |
| 305 | | Rolling research into a comprehensive marketing plan | `marketing-plan` | |
| 306 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Task Coordination StrategiesDecompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.◐◐◐◐◐●35/40Ebay Seller Tools·····●34/40Tough Decision Advisor: Every Angle ConsideredHand in a decision you're stuck on. Get back a clear breakdown of every angle — the trade-offs, the risks, the blind spot, and a recommended path.●····●32/40DHDNA Profiler — Cognitive Pattern ExtractionPaste any email, proposal, or note someone wrote, and get back a plain-language read on how they think, what drives their decisions, and how they communicate.●····●32/40