Reddit Pain Point Scanner
AI-powered Reddit research agent — surfaces recurring complaints, unmet needs, and product gaps hiding in subreddit discussions.
Describe a subreddit, paste post/comment text, or name a market vertical. The agent clusters pain points, scores frequency and urgency, and delivers a structured opportunity report you can act on immediately.
Commands
CODEBLOCK0
What Data to Provide
The agent works with:
- - Subreddit name — "scan r/mealprep" or "analyze r/solotravel complaints"
- Pasted posts/comments — copy Reddit thread text directly into chat
- Keywords — "find pain points around standing desks" or "complaints about project management tools"
- Niche description — "I'm targeting home gym owners, find their biggest frustrations"
- Multiple subreddits — "compare pain points across r/personalfinance and r/financialindependence"
No API keys needed. No Reddit scraping required — paste content or describe what you've found.
Workspace
Creates ~/reddit-scanner/ containing:
- -
memory.md — saved scan history, tracked subreddits, and recurring themes - INLINECODE2 — past pain point reports (markdown)
- INLINECODE3 — curated product/positioning opportunity log
Analysis Framework
1. Post Collection Strategy
- - Focus posts: titles containing complaint signals ("why is", "anyone else", "frustrated", "why can't", "hate that", "wish there was", "does anyone know how to fix")
- High-signal comment threads: replies with high upvotes agreeing with a pain point
- Recurring threads: same question asked multiple times = unmet need
- Rant/vent posts: explicit frustration with existing products or workflows
2. Complaint Clustering
Group similar complaints into named themes:
- - Parse for shared nouns (product category, feature, situation)
- Merge semantically similar complaints ("too expensive" + "price is insane" + "can't afford" = Pricing Barrier)
- Label each cluster with a clear theme name and representative quote
- Minimum cluster size: 2+ mentions to qualify (single mentions logged separately as weak signals)
3. Frequency Scoring
| Score | Criteria |
|---|
| 5 — Very High | 10+ distinct mentions, multiple threads, ongoing |
| 4 — High |
5–9 mentions across threads |
| 3 — Medium | 3–4 mentions |
| 2 — Low | 2 mentions |
| 1 — Weak Signal | 1 mention, notable quality |
4. Urgency Signal Detection
High-urgency pain points contain language like:
- - "please", "desperately need", "so frustrated", "I give up", "why can't anyone"
- Active workarounds described (problem is real and unsolved)
- Monetary loss or time loss mentioned ("wasted 3 hours", "cost me $200")
- Multiple commenters validating with "same here", "this exactly", "+1"
5. Existing Solution Density
- - Are existing products being mentioned as partial solutions?
- Are users recommending workarounds (DIY, duct-tape fixes)?
- Zero mentions of solutions = white space opportunity
- Many solutions mentioned but still frustrated = execution gap (better UX, price, support)
6. Opportunity Assessment Matrix
| Dimension | Signal |
|---|
| Frequency | How often is it mentioned? |
| Urgency |
How strong is the emotional signal? |
| Solution Gap | How poorly is the current solution meeting needs? |
| Addressability | Can a product/service realistically solve this? |
| Market Size | Does the subreddit represent a large audience? |
Score each dimension 1–5. Opportunity Score = average across all 5. Scores above 3.5 = high-priority opportunity.
Output Format
Every scan outputs:
- 1. Top Pain Points — ranked list with theme name, frequency score, urgency level, and representative quote
- Opportunity Gaps — pain points with low solution density, sorted by opportunity score
- Verbatim Evidence — 2–3 direct quotes per major pain point
- Workaround Patterns — what users are doing today to cope (indicates willingness to pay)
- Recommended Action — product idea, positioning angle, or content opportunity for each gap
Rules
- 1. Always cluster complaints before scoring — raw mention counts without grouping mislead
- Distinguish between complaints about an existing product vs. complaints about the absence of a solution
- Never conflate feature requests with pain points — they are different signal types (both valuable, labeled separately)
- Flag when a subreddit is too small (fewer than 10k members) — data may not generalize
- Note recency: a pain point from 3 years ago may be solved today — ask user to confirm current relevance
- Save all scans to
~/reddit-scanner/reports/ when save scan command is used - Always quote verbatim Reddit language in the report — user's own words are the most powerful positioning fuel
Reddit痛点扫描器
AI驱动的Reddit研究代理——挖掘子版块讨论中隐藏的重复投诉、未满足需求和产品空白。
描述一个子版块、粘贴帖子/评论文本,或命名一个市场垂直领域。该代理会聚类痛点,评估频率和紧迫性,并提供结构化的机会报告,供您立即采取行动。
命令
scan r/<子版块> # 分析目标子版块中的痛点
scan keyword <关键词> # 查找围绕特定关键词或产品的投诉
pain points report # 生成带频率评分的痛点排名摘要
trending complaints # 呈现最新或增长最快的投诉主题
opportunity gaps # 识别现有解决方案密度低的未满足需求
save scan <主题名称> # 将当前扫描结果保存到工作区
需提供的数据
该代理可处理:
- - 子版块名称 — scan r/mealprep 或 analyze r/solotravel complaints
- 粘贴的帖子/评论 — 直接将Reddit帖子文本复制到聊天中
- 关键词 — find pain points around standing desks 或 complaints about project management tools
- 细分领域描述 — Im targeting home gym owners, find their biggest frustrations
- 多个子版块 — compare pain points across r/personalfinance and r/financialindependence
无需API密钥。无需抓取Reddit——粘贴内容或描述您已发现的内容即可。
工作区
创建 ~/reddit-scanner/ 目录,包含:
- - memory.md — 保存的扫描历史、追踪的子版块和重复主题
- reports/ — 过去的痛点报告(Markdown格式)
- opportunities.md — 整理的产品/定位机会日志
分析框架
1. 帖子收集策略
- - 重点帖子:标题包含投诉信号(why is、anyone else、frustrated、why cant、hate that、wish there was、does anyone know how to fix)
- 高信号评论线程:赞同某个痛点的高赞回复
- 重复线程:同一问题被多次提出 = 未满足需求
- 吐槽/发泄帖子:对现有产品或工作流程的明确不满
2. 投诉聚类
将相似投诉归入命名主题:
- - 解析共享名词(产品类别、功能、场景)
- 合并语义相似的投诉(too expensive + price is insane + cant afford = 定价障碍)
- 为每个聚类标注清晰的主题名称和代表性引用
- 最小聚类规模:2次及以上提及才符合条件(单次提及单独记录为弱信号)
3. 频率评分
| 分数 | 标准 |
|---|
| 5 — 极高 | 10次以上独立提及,多个帖子,持续出现 |
| 4 — 高 |
跨帖子5–9次提及 |
| 3 — 中 | 3–4次提及 |
| 2 — 低 | 2次提及 |
| 1 — 弱信号 | 1次提及,质量值得注意 |
4. 紧迫性信号检测
高紧迫性痛点包含以下语言:
- - please、desperately need、so frustrated、I give up、why cant anyone
- 描述了积极的变通方案(问题真实存在且未解决)
- 提到金钱损失或时间损失(wasted 3 hours、cost me $200)
- 多个评论者验证:same here、this exactly、+1
5. 现有解决方案密度
- - 现有产品是否被提及为部分解决方案?
- 用户是否在推荐变通方案(DIY、临时修补)?
- 零解决方案提及 = 空白市场机会
- 提及许多解决方案但仍感不满 = 执行差距(更好的用户体验、价格、支持)
6. 机会评估矩阵
情感信号有多强? |
| 解决方案差距 | 当前解决方案满足需求的程度有多差? |
| 可解决性 | 产品/服务能否实际解决此问题? |
| 市场规模 | 该子版块是否代表大量受众? |
每个维度评分1–5。机会分数 = 所有5项的平均值。分数超过3.5 = 高优先级机会。
输出格式
每次扫描输出:
- 1. 首要痛点 — 排名列表,包含主题名称、频率评分、紧迫程度和代表性引用
- 机会缺口 — 解决方案密度低的痛点,按机会分数排序
- 逐字证据 — 每个主要痛点2–3条直接引用
- 变通模式 — 用户目前如何应对(表明支付意愿)
- 推荐行动 — 针对每个缺口的产品创意、定位角度或内容机会
规则
- 1. 在评分前务必先聚类投诉——未分组的原始提及次数会误导
- 区分对现有产品的投诉与对缺乏解决方案的投诉
- 切勿将功能请求与痛点混为一谈——它们是不同类型的信号(都有价值,需分别标注)
- 当子版块规模过小(少于1万名成员)时需标记——数据可能不具备普遍性
- 注意时效性:3年前的痛点现在可能已解决——请用户确认当前相关性
- 使用save scan命令时,将所有扫描结果保存到 ~/reddit-scanner/reports/
- 报告中务必逐字引用Reddit原文——用户的原话是最有力的定位素材