Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions. Use this when the customer is being guessed at, before positioning or a major launch, when churn or conversion has an unexplained cause, or when a team is arguing from anecdotes. Also use to turn raw interview notes into usable findings.
npx skills add https://github.com/cbrock84/headcount --skill customer-research
Research earns its cost only if a decision hangs on it. Name that decision before recruiting anyone.
from assumptions returns your assumptions.
and are systematically under-sampled.
Ask about the past, not the future. "What did you do last time" is evidence; "would you use this"
is politeness.
substance is.
want to hear, the interview is over.
problem.
Code the transcripts before forming a view — findings assembled to support an existing belief will
be. For each finding record: the claim, how many independently said it, a verbatim quote, and what
would change if it is true. A finding that changes nothing is trivia.
Separate what people said, what they did, and what you inferred. Conflating the three is
the most common way research misleads.
Take cbrock84/customer-research from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.