菜单
Use when monitoring online forums (Reddit, HN, ProductHunt) for recurring user pain points, feature requests, and unmet needs. Invoke for market research, pain-point discovery, trend detection, and competitive intelligence. Designed for scheduled execution via CronCreate.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/oimiragieo/agent-studio --skill forum-monitor命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Agent frontmatter enhancements — disallowedTools, mcpServers scoping, fork_eligible field
Context management — pre-compact persistence, threshold alignment, microcompact/circuit breaker detection
Hook enhancements — updatedInput for bash safety prefixes, suppressOutput for verbose blocks, denial-based routing feedback
正在显示 SKILL.md
基于 SOC 职业分类
| name | forum-monitor |
| description | Use when monitoring online forums (Reddit, HN, ProductHunt) for recurring user pain points, feature requests, and unmet needs. Invoke for market research, pain-point discovery, trend detection, and competitive intelligence. Designed for scheduled execution via CronCreate. |
| version | 1.0.0 |
| model | sonnet |
| invoked_by | both |
| user_invocable | true |
| tools | ["Read","Write","Bash","WebSearch","WebFetch","MemoryRecord"] |
| agents | ["forum-monitor-agent","researcher"] |
| category | research |
| tags | ["forum","reddit","hackernews","producthunt","pain-points","market-research","trend-detection","nlp","cron"] |
| best_practices | ["Always cite source URLs for every finding","Cross-reference at least 2 forums before reporting a trend","Use weighted opportunity scoring, not subjective assessment","Include verbatim user quotes as primary evidence","Design reports for downstream consumption by app-generator-agent"] |
| error_handling | graceful |
| streaming | supported |
| verified | true |
| lastVerifiedAt | 2026-03-21 |
| source | builtin |
| trust_score | 100 |
| provenance_sha | d63e410901559410 |
Systematic workflow for monitoring online communities to discover recurring user pain points. Transforms unstructured forum discussions into ranked, evidence-backed opportunity reports suitable for automated app generation pipelines.
Core principle: Pain points with high frequency and high engagement are the strongest product signals. Monitor, classify, rank, report.
This skill is designed to run on a schedule via CronCreate:
CronCreate({
name: 'weekly-forum-scan',
schedule: '0 9 * * MON', // Every Monday at 9 AM
prompt:
'Run forum monitor scan for [target domain]. Invoke Skill({ skill: "forum-monitor" }). Save report to .claude/context/reports/backend/',
});
Define the forums to monitor based on the target domain:
Forum Selection Matrix:
| Forum | Best For | Query Pattern |
|---|---|---|
| Consumer pain points, UX issues | site:reddit.com <topic> frustrating OR wish | |
| Hacker News | Developer tools, B2B SaaS | site:news.ycombinator.com <topic> |
| ProductHunt | New product gaps, feature envy | site:producthunt.com <topic> |
| Indie Hackers | Solo dev pain points, pricing | site:indiehackers.com <topic> |
| Dev.to | Developer workflow friction | site:dev.to <topic> pain OR annoy |
Query Templates:
"{topic} frustrating OR annoying OR wish OR need OR missing"
"{topic} alternative to OR better than OR looking for"
"{topic} feature request OR roadmap OR please add"
For each configured forum, execute searches and extract content:
// Search for pain points
WebSearch({ query: 'site:reddit.com {topic} frustrating OR wish OR need 2026' });
// Fetch specific threads with high engagement
WebFetch({
url: '{thread-url}',
prompt:
'Extract all complaints, feature requests, and pain points. For each, note the exact quote, upvote count, and whether others agreed.',
});
Collection Requirements:
Categorize each collected item into one of these categories:
| Category | Signal Words | Example |
|---|---|---|
missing-feature | "wish", "need", "please add", "roadmap" | "I wish Notion had offline mode" |
workflow-friction | "slow", "clunky", "takes forever" | "It takes 10 clicks to export a PDF" |
bug-report | "broken", "crashes", "error" | "The app crashes on large files" |
pricing | "expensive", "not worth", "free alt" | "Too expensive for a solo dev" |
ux-confusion | "confusing", "can't find", "intuitive" | "I had no idea where settings were" |
integration-gap | "connect to", "integrate with", "API" | "No Zapier integration available" |
Group similar pain points into clusters:
For each cluster, compute:
Opportunity Score = (Frequency x 0.4) + (Engagement x 0.3) + (Recency x 0.2) + (Sentiment Intensity x 0.1)
Where:
Write structured output to .claude/context/reports/backend/forum-monitor-report-{YYYY-MM-DD}.md:
<!-- Agent: forum-monitor-agent | Task: #{id} | Session: {date} -->
# Forum Monitor Report
**Scan Period**: {start-date} to {end-date}
**Forums Monitored**: {list}
**Total Posts Analyzed**: {count}
**Pain Point Clusters Found**: {count}
## Top Pain Points (Ranked by Opportunity Score)
| Rank | Pain Point | Category | Freq | Engagement | Score | Sources |
| ---- | ---------- | -------- | ---- | ---------- | ----- | ------- |
| 1 | [desc] | [cat] | [n] | [n] | [n.n] | [n] |
## Detailed Findings
### 1. [Pain Point Title] (Score: X.X)
**Category**: [type]
**Frequency**: [n] mentions across [n] sources
**Engagement**: [total upvotes] upvotes, [total comments] comments
**Forums**: [list of forums where this appeared]
**Representative Quotes:**
1. "[exact quote]" - [source URL] ([n] upvotes)
2. "[exact quote]" - [source URL] ([n] upvotes)
3. "[exact quote]" - [source URL] ([n] upvotes)
**App Opportunity Assessment:**
- Buildable as standalone app: YES/NO
- Estimated complexity: LOW/MEDIUM/HIGH
- Existing solutions: [list or "none found"]
- Differentiation angle: [what would make a new solution win]
| Anti-Pattern | Why It Fails | Correct Approach |
|---|---|---|
| Single-forum reports | One community is not representative | Cross-reference 2+ forums before trending |
| Subjective ranking | Personal opinion is not data | Use weighted opportunity formula |
| Missing source URLs | Downstream agents cannot validate findings | Every finding must have a clickable source |
| Stale data without date range | Trends from 2024 are not 2026 trends | Always specify scan period in report header |
| Over-counting duplicates | Same user posting in 3 threads is not 3 data points | Deduplicate by unique user + unique complaint |
browser-automation -- for deeper scraping when WebSearch/WebFetch are insufficientdeep-research -- for comprehensive investigation of specific pain pointsfeedback-analysis -- for structured sentiment and NPS analysis| Agent | Role |
|---|---|
forum-monitor-agent | Primary -- executes the full workflow |
researcher | Supporting -- deeper investigation |
app-generator-agent | Consumer -- reads reports for app ideas |
Before starting:
node .claude/lib/memory/memory-search.cjs "forum monitor pain points trends"
Read .claude/context/memory/learnings.md
After completing:
.claude/context/memory/learnings.md.claude/context/memory/issues.md.claude/context/memory/decisions.mdASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.