customer-research

Name: customer-research
Author: coreyhaines31

bycoreyhaines31· 76 skills

Installs

71k

Stars

42k

Forks

6.6k

How to install customer-research?

coreyhaines31/marketingskills/customer-research

$npx -y skills add coreyhaines31/marketingskills --skill customer-research

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Use this skill

Run `npx skills use "https://github.com/coreyhaines31/marketingskills" --skill "coreyhaines31/marketingskills/customer-research"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the whole pack

Use the skills in "https://github.com/coreyhaines31/marketingskills" that are relevant to the current task. Run `npx skills add "https://github.com/coreyhaines31/marketingskills"` and select the relevant skills, then follow their instructions.

Files · 1

View on GitHub

SKILL.md

1	# Customer Research
2
3	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.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	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.
9
10	---
11
12	## Two Modes of Research
13
14	### Mode 1: Analyze Existing Assets
15	You have raw research material (transcripts, surveys, reviews, tickets). Your job is to extract signal.
16
17	### Mode 2: Go Find Research
18	You need to gather intel from online sources (Reddit, G2, forums, communities, review sites). Your job is to know where to look and what to extract.
19
20	Most engagements combine both. Establish which mode applies before proceeding.
21
22	---
23
24	## Mode 1: Analyzing Existing Research Assets
25
26	### Asset Types
27
28	Customer interview / sales call transcripts
29	- Extract: pains, triggers, desired outcomes, language used, objections, alternatives considered
30	- Look for: the moment they decided to look for a solution, what they tried before, what success looks like to them
31
32	Survey results
33	- Segment responses by customer tier, use case, or tenure before drawing conclusions
34	- Flag: what open-ended answers say vs. what multiple-choice answers say (they often conflict)
35	- Identify: the 20% of responses that contain the most useful signal
36
37	Customer support conversations
38	- Mine for: recurring complaints, confusion points, feature requests, and "I wish it could…" language
39	- Categorize tickets before analyzing — don't treat all tickets as equal signal
40	- Separate bugs from confusion from missing features from expectation mismatches
41
42	Win/loss interviews and churned customer notes
43	- Wins: what tipped the decision? What almost made them choose a competitor?
44	- Losses and churn: was it price, features, fit, timing, or something else?
45	- Segment by reason — don't average across different churn causes
46
47	NPS responses
48	- Passives and detractors are higher signal than promoters for improvement work
49	- Pair scores with verbatims — a 9 with a specific complaint beats a 10 with no comment
50
51	### Extraction Framework
52
53	For each asset, extract:
54
55	1. Jobs to Be Done — what outcome is the customer trying to achieve?
56	- Functional job: the task itself
57	- Emotional job: how they want to feel
58	- Social job: how they want to be perceived
59
60	2. Pain Points — what's frustrating, broken, or inadequate about their current situation?
61	- Prioritize pains mentioned unprompted and with emotional language
62
63	3. Trigger Events — what changed that made them seek a solution?
64	- Common triggers: team growth, new hire, missed target, embarrassing incident, competitor doing something
65
66	4. Desired Outcomes — what does success look like in their words?
67	- Capture exact quotes, not paraphrases
68
69	5. Language and Vocabulary — exact words and phrases customers use
70	- This is gold for copy. "We were drowning in spreadsheets" > "manual process inefficiency"
71
72	6. Alternatives Considered — what else did they look at or try?
73	- Includes doing nothing, hiring someone, or building internally
74
75	### Synthesis Steps
76
77	After extracting from individual assets:
78
79	1. Cluster by theme — group similar pains, outcomes, and triggers across assets
80	2. Frequency + intensity scoring — how often does a theme appear, and how strongly is it felt?
81	3. Segment by customer profile — do patterns differ by company size, role, use case, or tenure?
82	4. Identify the "money quotes" — 5-10 verbatim quotes that best represent each theme
83	5. Flag contradictions — where do customers say one thing but do another?
84
85	### Research Quality Guardrails
86
87	Label every insight with a confidence level before presenting it:
88
89	\| Confidence \| Criteria \|
90	\|------------\|----------\|
91	\| High \| Theme appears in 3+ independent sources; mentioned unprompted; consistent across segments \|
92	\| Medium \| Theme appears in 2 sources, or only prompted, or limited to one segment \|
93	\| Low \| Single source; could be an outlier; needs validation \|
94
95	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.
96
97	Sample bias checks:
98	- Online reviewers skew toward power users and people with strong opinions
99	- Support tickets skew toward problems, not value
100	- Reddit skews technical and skeptical vs. mainstream buyers
101	- Factor this in when drawing conclusions about "all customers"
102
103	Minimum viable sample: Don't build personas or draw messaging conclusions from fewer than 5 independent data points per segment.
104
105	---
106
107	## Mode 2: Digital Watering Hole Research
108
109	Online communities are where customers speak without a filter. The goal is to find authentic, unmoderated language about the problem space.
110
111	### Where to Look
112
113	Choose sources based on your ICP type — then read `references/source-guides.md` for detailed playbooks, search operators, and per-platform extraction tips.
114
115	\| ICP Type \| Primary Sources \|
116	\|----------\|----------------\|
117	\| B2B SaaS / technical buyers \| Reddit (role-specific subs), G2/Capterra, Hacker News, LinkedIn, Indie Hackers, SparkToro \|
118	\| SMB / founders \| Reddit (r/entrepreneur, r/smallbusiness), Indie Hackers, Product Hunt, Facebook Groups, SparkToro \|
119	\| Developer / DevOps \| r/devops, r/programming, Hacker News, Stack Overflow, Discord servers \|
120	\| B2C / consumer \| App store reviews (1-3 star), Reddit hobby/lifestyle subs, YouTube comments, TikTok/Instagram comments \|
121	\| Enterprise \| LinkedIn, industry analyst reports, G2 Enterprise filter, job postings, SparkToro \|
122
123	Quick decision guide:
124	- Have a product category? → Start with G2/Capterra reviews (yours + competitors)
125	- Need to know where your audience spends time? → SparkToro (reveals podcasts, YouTube, subreddits, websites, social accounts)
126	- Need raw language? → Reddit and YouTube comments
127	- Need trigger events? → LinkedIn posts, job postings, Hacker News "Ask HN" threads
128	- Need competitive intel? → Competitor 4-star reviews on G2; Product Hunt discussions; SparkToro competitor audience analysis
129
130	### What to Extract from Each Source
131
132	For every piece of content you find:
133
134	\| Field \| What to Capture \|
135	\|-------\|----------------\|
136	\| Source \| Platform, thread URL, date \|
137	\| Verbatim quote \| Exact words — don't paraphrase \|
138	\| Context \| What prompted the comment? \|
139	\| Sentiment \| Positive / negative / neutral / frustrated \|
140	\| Theme tag \| Pain / trigger / outcome / alternative / language \|
141	\| Customer profile signals \| Role, company size, industry hints from the post \|
142
143	### Research Synthesis Template
144
145	After gathering from multiple sources, synthesize into:
146
147	```
148	## Top Themes (ranked by frequency × intensity)
149
150	### Theme 1: [Name]
151	Summary: [1-2 sentences]
152	Frequency: Appeared in X of Y sources
153	Intensity: High / Medium / Low (based on emotional language used)
154	Representative quotes:
155	- "[exact quote]" — [source, date]
156	- "[exact quote]" — [source, date]
157	Implications: What this means for messaging / product / positioning
158
159	### Theme 2: ...
160	```
161
162	---
163
164	## Persona Generation
165
166	### When there are no reviews yet
167
168	Early-stage products (or new categories) lack first-party review data. Don't invent personas — walk outward through proxy sources, in order:
169
170	1. Your own differentiator — what the product does differently defines who feels that difference most; write the hypothesis down as a hypothesis
171	2. Direct competitors' reviews — their customers describe the problem space in their words (note what's praised and what's missing)
172	3. Comparable products on marketplaces — Amazon/app-store reviews for adjacent solutions to the same job
173	4. Adjacent brands sharing the audience — what else this buyer buys; their reviews reveal the buyer's broader language and values
174
175	Personas built this way are provisional: tag each with its proxy source, and replace proxy evidence with first-party evidence as real reviews arrive.
176
177
178	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.
179
180	### Persona Structure
181
182	```
183	## [Persona Name] — [Role/Title]
184
185	Profile
186	- Title range: [e.g., "Marketing Manager to VP of Marketing"]
187	- Company size: [e.g., "50–500 employees, Series A–C SaaS"]
188	- Industry: [if narrow]
189	- Reports to: [who]
190	- Team size managed: [if relevant]
191
192	Primary Job to Be Done
193	[One sentence: what outcome are they trying to achieve in their role?]
194
195	Trigger Events
196	What causes them to start looking for a solution like yours?
197	- [trigger 1]
198	- [trigger 2]
199
200	Top Pains
201	1. [Pain — in their words if possible]
202	2. [Pain]
203	3. [Pain]
204
205	Desired Outcomes
206	- [What success looks like to them]
207	- [How they measure it]
208	- [How it makes them look to their boss/team]
209
210	Objections and Fears
211	- [What makes them hesitate to buy or switch]
212
213	Alternatives They Consider
214	- [Competitor, DIY, do nothing, hire someone]
215
216	Key Vocabulary
217	Words and phrases they actually use (sourced from research):
218	- "[phrase]"
219	- "[phrase]"
220
221	How to Reach Them
222	- Channels: [where they spend time]
223	- Content they consume: [formats, topics]
224	- Influencers/communities they trust: [specific names if known]
225	```
226
227	### Persona Anti-Patterns
228
229	- Don't name them cutely ("Marketing Mary") unless your team finds it helpful — it's often a distraction
230	- Don't average across segments — a persona that represents everyone represents no one
231	- Don't invent details — if you don't have data on something, leave it blank rather than filling it in
232	- Revisit quarterly — personas decay as your market and product evolve
233
234	---
235
236	## Deliverable Formats
237
238	Depending on what the user needs, offer:
239
240	1. Research synthesis report — themes, quotes, patterns, and implications
241	2. VOC quote bank — organized verbatim quotes by theme, for use in copy
242	3. Persona document — 1-3 personas built from the research
243	4. Jobs-to-be-done map — functional, emotional, and social jobs by segment
244	5. Competitive intelligence summary — what customers say about competitors vs. you
245	6. Research gap analysis — what you still don't know and how to find it
246
247	Ask the user which deliverable(s) they need before generating output.
248
249	---
250
251	## Questions to Ask Before Proceeding
252
253	If context is unclear:
254
255	1. What's the goal? Improve messaging? Build personas? Find product gaps? Understand churn?
256	2. What do you already have? (transcripts, surveys, tickets, G2 reviews, nothing)
257	3. Who is the target segment? (all customers, a specific tier, churned users, prospects who didn't buy)
258	4. What's your product? (if not in the product marketing context file)
259	5. What do you want delivered? (synthesis report, persona, quote bank, competitive intel)
260
261	Don't ask all five at once — lead with #1 and #2, then follow up as needed.
262
263	---
264
265	## Related Skills
266
267	\| When to hand off \| Skill \|
268	\|-----------------\|-------\|
269	\| Writing copy informed by the research \| `copywriting` \|
270	\| Optimizing a page using VOC insights \| `cro` \|
271	\| Building a competitor comparison page \| `competitors` \|
272	\| Creating a churn prevention strategy from churn research \| `churn-prevention` \|
273	\| Planning paid ads informed by research \| `ads` \|
274	\| Writing cold email using research on pain/trigger \| `cold-email` \|
275	\| Translating customer research into an ICP for outbound \| `prospecting` \|
276	\| Planning content based on discovered topics \| `content-strategy` \|
277	\| Rolling research into a comprehensive marketing plan \| `marketing-plan` \|

6 picks

Type

Run `npx skills use "https://github.com/coreyhaines31/marketingskills" --skill "coreyhaines31/marketingskills/customer-research"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the skills in "https://github.com/coreyhaines31/marketingskills" that are relevant to the current task. Run `npx skills add "https://github.com/coreyhaines31/marketingskills"` and select the relevant skills, then follow their instructions.

customer-research

How to install customer-research?

Related

customer-research

How to install customer-research?

Related