customer-research
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 researc
Security Assessment
About customer-research
The customer-research skill enables users to systematically uncover and understand customer needs, behaviors, and preferences. It solves the common problem of making product, marketing, or copy decisions based on assumptions rather than real insights. By providing structured methods for analyzing existing research and gathering new data from online sources, this skill ensures that strategies are grounded in actual customer experiences. It focuses on extracting actionable insights from raw materials such as interviews, surveys, support tickets, win/loss notes, NPS responses, and public online discussions, allowing teams to identify true pain points, triggers, and desired outcomes.
FAQ
What types of research assets can this skill analyze?
This skill can analyze customer interviews, sales call transcripts, survey results, support conversations, win/loss interviews, churn notes, and NPS responses. It extracts insights such as pain points, triggers, desired outcomes, and the language customers use.
Can this skill gather new customer research from online sources?
Yes, it can gather intelligence from online sources including Reddit, review sites like G2, forums, communities, and other digital spaces where customers discuss their experiences.
Do I need prior context about the product before using this skill?
It is recommended to check for existing product marketing context documents before starting, as they may answer questions and reduce redundant research.
Are there any limitations when analyzing support tickets or surveys?
Yes, not all tickets or survey responses carry equal signal. Tickets should be categorized to separate bugs, confusion, or missing features, and survey responses should be segmented and prioritized to focus on the most informative 20%.
Who is the intended user for this skill?
The skill is designed for customer researchers, product managers, marketers, UX designers, or anyone seeking to ground decisions in real customer insights.
Install customer-research
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
coreyhaines31/marketingskills