Review Mining
shawnpang/startup-founder-skills
When the user wants to research customer pain points, complaints, or sentiment using review platforms like Trustpilot, G2, Capterra, or app stores.
Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer.
Install Voice Of Customer
$ npx skills add cbrock84/headcount --skill voice-of-customer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount voice-of-customer --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/customer-experience/skills/voice-of-customer .claude/skills/voice-of-customer && 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 "voice-of-customer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/voice-of-customer into .claude/skills/voice-of-customer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-of-customer", 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/customer-experience/skills/voice-of-customerType 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 voice-of-customer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount voice-of-customer --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/customer-experience/skills/voice-of-customer .agents/skills/voice-of-customer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "voice-of-customer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/voice-of-customer into .agents/skills/voice-of-customer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-of-customer", 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 voice-of-customer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount voice-of-customer --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/customer-experience/skills/voice-of-customer .cursor/skills/voice-of-customer && 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 "voice-of-customer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/voice-of-customer into .cursor/skills/voice-of-customer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-of-customer", 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/customer-experience/skills/voice-of-customer--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 voice-of-customer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount voice-of-customer --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/customer-experience/skills/voice-of-customer .gemini/skills/voice-of-customer && 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 "voice-of-customer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/voice-of-customer into .gemini/skills/voice-of-customer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-of-customer", 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 voice-of-customerInstalls 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 voice-of-customer -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/customer-experience/skills/voice-of-customer .github/skills/voice-of-customer && 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 "voice-of-customer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/voice-of-customer into .github/skills/voice-of-customer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-of-customer", 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 voice-of-customer -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 voice-of-customer --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/customer-experience/skills/voice-of-customer .opencode/skills/voice-of-customer && 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 "voice-of-customer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/voice-of-customer into .opencode/skills/voice-of-customer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "voice-of-customer", 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
voice-of-customer- GitHub stars
- 2k
- Token cost
- ~1k tokens
- SKILL.md length
- 539 words
- Files
- 1
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer.
- Tasks that involve Customer feedback analysis
- SKILL.md covers Sources, weighted honestly, On CSAT and NPS, Turning feedback into change and Closing the loop, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Market research
What it does
Voice Of Customer is an agent skill from cbrock84/headcount. Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Customer feedback analysis and 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
- Tasks that involve Customer feedback analysis
- Tasks that involve Market research
Example prompts
- “Use the voice-of-customer skill to build the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from…”
- “/voice-of-customer”
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
Voice Of Customer loads about 1k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 539 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). 539 words, ~1,004 tokens.
Download SKILL.mdSave it as
.claude/skills/voice-of-customer/SKILL.md (or your agent's skills folder).- name
- voice-of-customer
- description
- Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.
Voice of customer
Most feedback programs collect diligently and change nothing. The collection is the easy half; the loop is the whole value.
Sources, weighted honestly
- Support contacts — the highest-volume and least prompted source, and the most under-used. People contacting you have a real problem nobody asked them about. But the sample is strongly self-selected: it excludes everyone who silently churned, worked around the problem, or would never contact you. Treat it as operational evidence to be normalized per active account and triangulated against churn and behavioral data — never as representative of the customer base.
- Churn and loss reasons — the most valuable and most under-sampled. People leaving have no reason to be polite.
- Interviews — depth, small n, best for understanding why something in the data is happening.
- Surveys — breadth, and only meaningful once you know what to ask.
- Public reviews and forums — biased toward extremes, useful for what people say when you are not in the room.
Anything a customer built a workaround for outranks anything they merely said in a survey.
On CSAT and NPS
Both are useful as trends and misleading as targets. The moment a team is measured on a score, the score improves faster than the experience does — asking at the favorable moment, coaching for the rating, excluding difficult segments.
Treat the score as a prompt for the free-text answer, which is where the information is. Segment before concluding: an overall score is an average of experiences that have nothing in common.
Never target a number without also watching the behavior it is supposed to predict.
Turning feedback into change
The failure is not collection, it is triage. Feedback needs:
- Categorization against a stable taxonomy, so volume per cause is countable across periods.
- Quantification. "Several customers mentioned" loses every argument. "Eighty-one contacts this quarter, four percent of active accounts, twelve of them on enterprise plans" wins.
- A named owner per theme, outside the feedback function. A theme owned by the team collecting it goes nowhere.
- A standing review where product, support, and success look at the same list together.
Distinguish requests from problems. Customers describe solutions; your job is to recover the problem underneath, because the request is often not the best fix for it.
Show full SKILL.md (170 more words)Show less
Closing the loop
Tell the customer what changed and that they prompted it. Almost nobody does this, which is exactly why it works — it converts a complainer into someone who reports the next issue instead of leaving.
Also close it internally: show the support team what shipped because of what they escalated, or they stop escalating.
Tooling
Survey and feedback: Qualtrics, Medallia, Delighted, SurveyMonkey, Typeform, and similar.
In-product feedback and micro-surveys: Pendo, Sprig, Chameleon, and similar — usually a better signal than emailed surveys because they reach people mid-task rather than after the fact.
Aggregating unstructured feedback across tickets, calls and reviews is where the platforms differ most. Whatever collects it, the theme has to be traceable back to individual verbatims, or nobody downstream will believe the count.
Never
- Report themes without volume.
- Let one loud enterprise account set the roadmap without checking how widely the problem is shared.
- Run a program with no mechanism for anything to change as a result. That is a survey habit, not a feedback loop.
© 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
Just SKILL.md in plugins/customer-experience/skills/voice-of-customer of cbrock84/headcount.
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Voice Of Customer 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 |
|---|---|---|---|---|---|---|
| Voice Of Customer this skillcbrock84/headcount | 2k | — | ~1k | Automated safety check: Pass | MIT | |
| Review Miningshawnpang/startup-founder-skills | 343 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Voice Of Customer Synthesizergooseworks-ai/goose-skills | 1.2k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Analyze Feedbackamplitude/builder-skills | 159 | — | ~942 | Automated safety check: Pass | None | |
| Memstack Product Feedback Analyzercwinvestments/memstack | 423 | — | ~2.7k | Automated safety check: Pass | Proprietary | |
| Voice Of Customergtmagents/gtm-agents | 414 | 1 repos | ~338 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Voice Of Customer Synthesizer
gooseworks-ai/goose-skills
Aggregate customer feedback from multiple sources — support tickets, NPS comments, Slack messages, G2 reviews, call transcripts, survey responses — into a unified VoC report with theme clustering…
Analyze Feedback
amplitude/builder-skills
Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise.
Memstack Product Feedback Analyzer
cwinvestments/memstack
A skill your agent uses when the user says 'analyze feedback', 'feedback analysis', 'what are customers asking for', or has support tickets, reviews, or survey data to categorize, score, and…
Voice Of Customer
gtmagents/gtm-agents
A skill your agent uses to design, run, and synthesize customer feedback programs tied to journey stages.
Voice Of Customer Program
mohitagw15856/pm-claude-skills
Stand up a Voice of Customer (VoC) program that turns feedback into action.
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 Voice Of Customer
What does Voice Of Customer do?
Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Voice Of Customer is an agent skill from cbrock84/headcount. Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer.
When should I use Voice Of Customer?
Voice Of Customer fits situations like: tasks that involve Customer feedback analysis; tasks that involve Market research.
How do I install Voice Of Customer in Claude Code?
Run `npx skills add cbrock84/headcount --skill voice-of-customer -a claude-code`. Or copy the skill folder (plugins/customer-experience/skills/voice-of-customer in cbrock84/headcount) into .claude/skills/voice-of-customer in your project. Claude Code loads it when a task matches its description.
How do I install Voice Of Customer in Codex?
Run `npx skills add cbrock84/headcount --skill voice-of-customer -a codex`. Or copy the skill folder (plugins/customer-experience/skills/voice-of-customer in cbrock84/headcount) into .agents/skills/voice-of-customer in your project. Codex loads it when a task matches its description.
Can I use Voice Of Customer 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 voice-of-customer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/voice-of-customer, .gemini/skills/voice-of-customer, .github/skills/voice-of-customer and .opencode/skills/voice-of-customer in your project.
What does Voice Of Customer need to run?
SKILL.md names no scripts, command-line tools or credentials: Voice Of Customer is instructions for the agent only.
Does Voice Of Customer 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 Voice Of Customer 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 Voice Of Customer use?
Voice Of Customer 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 Voice Of Customer use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Voice Of Customer?
Skills that share tags, products or a category with Voice Of Customer: Review Mining (shawnpang/startup-founder-skills, 343 stars), Voice Of Customer Synthesizer (gooseworks-ai/goose-skills, 1.2k stars), Analyze Feedback (amplitude/builder-skills, 159 stars) and Memstack Product Feedback Analyzer (cwinvestments/memstack, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Voice Of Customer?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 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.