Buyer discovery — run the discover pass on the audience axis: who the people the product serves are (self-names observed with citations) and where they talk about their own situation in public. TRIGGER when the market thread needs its buyer groups and sources enumerated before any one is mined. DO NOT TRIGGER to extract quotes from one source (research-problem), to study a competitor's own pages including its review pages (research-competitor), or to draw the competitive set (discover-competi...
Scanned 9/5/2026
Install to Claude Code
npx -y skills add heyJordanParker/dotfiles --skill discover-audience --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Discover Audience?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/heyjordanparker-discover-audience)More formats (shields.io, HTML) on the badges page.
---
name: discover-audience
description: Buyer discovery — run the discover pass on the audience axis: who the people the product serves are (self-names observed with citations) and where they talk about their own situation in public. TRIGGER when the market thread needs its buyer groups and sources enumerated before any one is mined. DO NOT TRIGGER to extract quotes from one source (research-problem), to study a competitor's own pages including its review pages (research-competitor), or to draw the competitive set (discover-competitors).
---
# Discover Audience
Run /discover on the audience axis. Subject: the market thread. The base owns the sweep, the page gate, the trust check, the observed-facts-only rule, and the write into `research/<subject>/discovery/`. This skill adds only the audience axis below.
Inputs: the population the product serves, stated as people, from the research `Brief.md`. Excluded: owner facts, product facts, competitor records, any persona or target buyer, and any handed-in problem — the buyer and the problems are research outputs, and a guess handed in as input biases the whole thread.
## Sweep these source types
Where the people the product serves talk in the open, never on a named product's own pages. Ask: who are the sub-groups, and where do they describe their own situation? Enumerate long — the observed self-names they use, each with its citation, and the venues:
- **Forums and communities** — Reddit role and problem subreddits, Hacker News, Indie Hackers, Product Hunt discussion tabs, niche Slack and Discord.
- **Situation-phrase searches** — the words the people use about their own situation, surfacing the threads, blog comments, and Q&A where they describe it unprompted.
- **Job postings** — a posting is a company admitting the pain and naming the stack.
Per entry, record the buyer group it holds alongside the countable facts the base names — member or review count, post or thread activity, recency.
## Leave named-product review pages to the competitor track
A named product's review pages (G2, Capterra, app-store reviews) and its published testimonials or case studies are OUT of this thread — mining a named product means knowing the competitor, and buyer discovery stays blind to the competitor set. That work runs via research-competitor. Buyer discovery stays problem-space only.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!