Agent skill · marketing growth · deanpeters
voice-of-customer-miner
Mine public reviews, app stores, and forums for unmet needs, competitor weaknesses, and switching triggers — with quoted evidence. Use when you want customer voice without waiting on interviews.
Why this skill is useful
Provides domain-specific insights into customer sentiment and unmet needs that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-07-17. 6,302 stars on the source repository.
What this skill does
Voice-of-Customer Miner Purpose Mine public customer voice — review sites, app stores, Reddit and practitioner forums, community boards — for unmet needs, competitor weaknesses, and switching triggers: search plan → source sweep → verbatim capture → need themes → so what → next-step options. This bridges competitive intelligence and discovery: it delivers customers' exact words without waiting on an interview cycle. But public voice skews toward the angry and the vocal, so every theme it surfaces is a hypothesis to validate, never a verdict — the output's last stop is always a real conversation. Input Works best with: the product(s) or competitor(s) to mine — yours, a rival's, or a set — and the decision this should inform. Also useful: a theme to focus on (onboarding, pricing, reliability) if you have one; otherwise the sweep runs open. Input supplied inline with the invocation — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it against the question budget; don't re-ask. Arriving empty-handed? That works too. The skill opens with at most 3 questions (whose voice, what decision, theme or open sweep) and proceeds on labeled assumptions if they go unanswered. Example invocation: Mine voice-of-customer for [Competitor A] and [Competitor B], focus on onboarding — informs whether our Q1 bet is a migration tool. Key Concepts Governing protocol: honors the autonomous-investigation contract — question budget of 3, search-plan gate, Fact/Inference/Assumption labels, Just Enough Mode, stable schema, 4-option Final Step. Discipline: OSINT's review-and-community layer (see intelligence-collection-disciplines). Theme by need, not by feature. "Exports are broken" is a feature complaint; "I can't get my data where my team works" is the underlying need. Theming by need is the same solution-free discipline as JTBD and painstorming — and it's what makes themes portable into discovery. Verbatims are the product. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills deanpeters/voice-of-customer-miner