mcpbeat Sign in

Product Demand Research Agent 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. Produces evidence-backed product research.

635 tokens
context cost
SKILL.md, read when the skill is used
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1 780
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/ScrapeCreators/social-media-research-skills --skill product-demand-research

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting
WebFetch fetches pages from the network

The instruction itself

7 sections, as written by the author

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.

How to use it

Copy the folder

Take scrapecreators/product-demand-research from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.