Customer Research
Nexus-JPF/note-companion
When the user wants to conduct, analyze, or synthesize customer research.
Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions.
Install Customer Research
$ npx skills add cbrock84/headcount --skill customer-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount customer-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/marketing/skills/customer-research .claude/skills/customer-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "customer-research" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/customer-research into .claude/skills/customer-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/customer-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill customer-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount customer-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/marketing/skills/customer-research .agents/skills/customer-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "customer-research" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/customer-research into .agents/skills/customer-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill customer-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount customer-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/marketing/skills/customer-research .cursor/skills/customer-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "customer-research" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/customer-research into .cursor/skills/customer-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/marketing/skills/customer-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill customer-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount customer-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/marketing/skills/customer-research .gemini/skills/customer-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "customer-research" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/customer-research into .gemini/skills/customer-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount customer-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill customer-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/marketing/skills/customer-research .github/skills/customer-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "customer-research" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/customer-research into .github/skills/customer-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill customer-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount customer-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/marketing/skills/customer-research .opencode/skills/customer-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "customer-research" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/customer-research into .opencode/skills/customer-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
customer-research- GitHub stars
- 2k
- Token cost
- ~651 tokens
- SKILL.md length
- 346 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions.
- Turn raw interview notes into usable findings
- SKILL.md covers Choose the method by question, Interviewing, Synthesizing and Sources, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Market research
What it does
Customer Research is an agent skill from cbrock84/headcount. 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.
Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in Marketing & SEO, covering Market research. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
When your agent uses it
- Turn raw interview notes into usable findings
- Tasks that involve Market research
Example prompts
- “/customer-research”
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Customer Research loads about 651 tokens when it runs, and up to ~891 if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 346 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 346 words, ~651 tokens.
Download SKILL.mdSave it as
.claude/skills/customer-research/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- customer-research
- description
- 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.
Customer research
Research earns its cost only if a decision hangs on it. Name that decision before recruiting anyone.
Choose the method by question
- Why did this happen / what do they actually do — interviews. Small n, deep.
- How common is this — survey. Only after interviews have told you what to ask; a survey written from assumptions returns your assumptions.
- Why did we win or lose — win-loss, with losses weighted higher. Losses are where the truth is and are systematically under-sampled.
- Which framing works — message testing against a real choice, not a preference rating.
Interviewing
Ask about the past, not the future. "What did you do last time" is evidence; "would you use this" is politeness.
- Open broad, follow the energy, and go quiet after their first answer — the second one is where the substance is.
- Chase specifics: when, what happened next, what did that cost you, who else was involved.
- Never describe your solution before you have their problem in their words. Once they know what you want to hear, the interview is over.
- Watch for the workaround. Anything someone has built a spreadsheet to survive is a validated problem.
Synthesizing
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.
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Never
- Recruit only happy customers. The sample that answers your email is not your market.
- Lead: "How much would this feature help?" has one answer.
- Present a single interview as a finding.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/marketing/skills/customer-research of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Customer Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Customer Research this skillcbrock84/headcount | 2k | — | ~651 | Automated safety check: Pass | MIT | |
| Customer ResearchNexus-JPF/note-companion | 870 | 6 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Creative Directorsmixs/creative-director-skill | 248 | — | ~5.1k | Automated safety check: Pass | CC-BY-4.0 | |
| Audience ResearchScrapeCreators/social-media-research-skills | 3.4k | — | ~635 | Automated safety check: Notes | MIT | |
| Last 30 Days Trend Researchnexu-io/open-design | 100k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Bggg Data Redditbinggandata/bggg-skills | 604 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Creative Director
smixs/creative-director-skill
AI creative director with recursive self-assessment. An agent skill from smixs/creative-director-skill.
Audience Research
ScrapeCreators/social-media-research-skills
A skill your agent uses when the user wants to evaluate a creator, influencer, or brand audience using public profile signals, TikTok audience demographics, follower/following data, comments…
Last 30 Days Trend Research
nexu-io/open-design
Produces a cited Markdown briefing on recent community sentiment and social reaction to a topic, labeling every source it could not actually check.
Bggg Data Reddit
binggandata/bggg-skills
Collect auditable Reddit search results and full comment trees at scale, preserve the source JSON, and normalize posts and comments into analysis-ready JSONL.
Comment Mining
ScrapeCreators/social-media-research-skills
A skill your agent uses when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or…
More from cbrock84/headcount
All 178 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI ML Governance
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
Related
Categories
Questions about Customer Research
What does Customer Research do?
Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions. Customer Research is an agent skill from cbrock84/headcount. Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions.
When should I use Customer Research?
Customer Research fits situations like: turn raw interview notes into usable findings; tasks that involve Market research.
How do I install Customer Research in Claude Code?
Run `npx skills add cbrock84/headcount --skill customer-research -a claude-code`. Or copy the skill folder (plugins/marketing/skills/customer-research in cbrock84/headcount) into .claude/skills/customer-research in your project. Claude Code loads it when a task matches its description.
How do I install Customer Research in Codex?
Run `npx skills add cbrock84/headcount --skill customer-research -a codex`. Or copy the skill folder (plugins/marketing/skills/customer-research in cbrock84/headcount) into .agents/skills/customer-research in your project. Codex loads it when a task matches its description.
Can I use Customer Research in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill customer-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/customer-research, .gemini/skills/customer-research, .github/skills/customer-research and .opencode/skills/customer-research in your project.
What does Customer Research need to run?
SKILL.md names no scripts, command-line tools or credentials: Customer Research is instructions for the agent only.
Does Customer Research access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Customer Research safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Customer Research use?
Customer Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Customer Research use?
About 651 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 240 tokens, read only when the agent opens those files.
What are the alternatives to Customer Research?
Skills that share tags, products or a category with Customer Research: Customer Research (Nexus-JPF/note-companion, 870 stars), Creative Director (smixs/creative-director-skill, 248 stars), Audience Research (ScrapeCreators/social-media-research-skills, 3.4k stars) and Last 30 Days Trend Research (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Customer Research?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,016 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.