Product demand research skill
Use when the user wants to validate a product idea, find pain points, mine demand signals, discover objections, or gather voice-of-customer language from Reddit, social posts, video transcripts, and comments.
by ScrapeCreators·MIT license·★ 2,619 Stars on the repo·GitHub ↗
Use now
npx degit ScrapeCreators/social-media-research-skills/skills/product-demand-research#main ~/.claude/skills/product-demand-researchChecked ·commit main
Files of Product demand research
SKILL.md
Show the full text92 lines
Product Demand Research
Overview
Use public social data to understand whether people actually complain about, ask for, buy, hack around, or recommend solutions in a product category. The output should help founders and marketers decide what to build, position, or test.
When to Use
Use this skill when the user asks to:
- validate a startup or product idea
- find pain points in a niche
- mine Reddit/TikTok/YouTube comments for product ideas
- find buyer language and objections
- understand alternatives people use today
- create messaging from demand evidence
Signals to Extract
- repeated complaints
- "I wish" / "is there a tool" / "how do I" phrases
- workarounds and spreadsheets/manual processes
- comparison and alternative mentions
- buying intent
- objections to existing solutions
- exact words people use for the problem
Workflow
- Turn the idea into search queries and synonyms.
- Search Reddit and relevant social platforms.
- Pull comments/transcripts for promising posts/videos.
- Cluster pains, triggers, alternatives, and desired outcomes.
- Score demand by frequency, intensity, recency, and willingness-to-pay hints.
- Produce messaging and product implications.
Output Format
# Product Demand Research: {idea/category}
## Verdict
- Demand signal: Strong/Medium/Weak
- Confidence: High/Medium/Low
- Why:
## Pain Points
| Pain | Evidence | Exact language | Source |
|---|---|---|---|
## Existing Alternatives / Workarounds
- ...
## Objections and Barriers
- ...
## Messaging Angles
- "..."
## Product Ideas / Tests
1. ...
2. ...
Common Pitfalls
- Do not claim market validation from a handful of comments.
- Do not ignore negative evidence or existing alternatives.
- Do not paraphrase away the best customer language.
| 1 | |
| 2 | name product-demand-research |
| 3 | description Use when the user wants to validate a product idea, find pain points, mine demand signals, discover objections, or gather voice-of-customer language from Reddit, social posts, video transcripts, and comments. Produces evidence-backed product research. |
| 4 | allowed-tools Bash, Read, Write, WebFetch |
| 5 | |
| 6 | version 1.0.0 |
| 7 | author ScrapeCreators |
| 8 | license MIT |
| 9 | homepage https://scrapecreators.com |
| 10 | repository https://github.com/ScrapeCreators/social-media-research-skills |
| 11 | metadata |
| 12 | openclaw |
| 13 | requires |
| 14 | env |
| 15 | - SCRAPECREATORS_API_KEY |
| 16 | primaryEnv SCRAPECREATORS_API_KEY |
| 17 | homepage https://scrapecreators.com |
| 18 | tags |
| 19 | - social-media |
| 20 | - research |
| 21 | - scrapecreators |
| 22 | |
| 23 | |
| 24 | # Product Demand Research |
| 25 | |
| 26 | ## Overview |
| 27 | |
| 28 | Use public social data to understand whether people actually complain about, ask for, buy, hack around, or recommend solutions in a product category. The output should help founders and marketers decide what to build, position, or test. |
| 29 | |
| 30 | ## When to Use |
| 31 | |
| 32 | Use this skill when the user asks to: |
| 33 | |
| 34 | validate a startup or product idea |
| 35 | find pain points in a niche |
| 36 | mine Reddit/TikTok/YouTube comments for product ideas |
| 37 | find buyer language and objections |
| 38 | understand alternatives people use today |
| 39 | create messaging from demand evidence |
| 40 | |
| 41 | ## Signals to Extract |
| 42 | |
| 43 | repeated complaints |
| 44 | "I wish" / "is there a tool" / "how do I" phrases |
| 45 | workarounds and spreadsheets/manual processes |
| 46 | comparison and alternative mentions |
| 47 | buying intent |
| 48 | objections to existing solutions |
| 49 | exact words people use for the problem |
| 50 | |
| 51 | ## Workflow |
| 52 | |
| 53 | Turn the idea into search queries and synonyms. |
| 54 | Search Reddit and relevant social platforms. |
| 55 | Pull comments/transcripts for promising posts/videos. |
| 56 | Cluster pains, triggers, alternatives, and desired outcomes. |
| 57 | Score demand by frequency, intensity, recency, and willingness-to-pay hints. |
| 58 | Produce messaging and product implications. |
| 59 | |
| 60 | ## Output Format |
| 61 | |
| 62 | |
| 63 | # Product Demand Research: {idea/category} |
| 64 | |
| 65 | ## Verdict |
| 66 | - Demand signal: Strong/Medium/Weak |
| 67 | - Confidence: High/Medium/Low |
| 68 | - Why: |
| 69 | |
| 70 | ## Pain Points |
| 71 | | Pain | Evidence | Exact language | Source | |
| 72 | |---|---|---|---| |
| 73 | |
| 74 | ## Existing Alternatives / Workarounds |
| 75 | - ... |
| 76 | |
| 77 | ## Objections and Barriers |
| 78 | - ... |
| 79 | |
| 80 | ## Messaging Angles |
| 81 | - "..." |
| 82 | |
| 83 | ## Product Ideas / Tests |
| 84 | 1. ... |
| 85 | 2. ... |
| 86 | |
| 87 | |
| 88 | ## Common Pitfalls |
| 89 | |
| 90 | Do not claim market validation from a handful of comments. |
| 91 | Do not ignore negative evidence or existing alternatives. |
| 92 | Do not paraphrase away the best customer language. |
Discussion
Browse more free Claude skills.