solo-community-outreach

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/community-outreach

/社区推广工具

Find relevant community threads (Reddit, Hacker News, ProductHunt) and draft contextual, value-first responses. NOT spam — genuine helpful answers that naturally mention the product.

查找Reddit、Hacker News、ProductHunt上的相关社区讨论帖，起草贴合语境、以价值为核心的回复。严禁垃圾信息——要提供真正有帮助的答案，自然地提及产品。

MCP Tools (use if available)

MCP工具（如有可用请使用）

web_search(query, engines, include_raw_content)

— search Reddit (PullPush), HN, web

```
kb_search(query)
```
— find related methodology
```
project_info(name)
```
— get project details

If MCP tools are not available, use Claude WebSearch/WebFetch as fallback.

```
web_search(query, engines, include_raw_content)
```
—— 搜索Reddit（通过PullPush）、HN、网页
```
kb_search(query)
```
—— 查找相关方法论
```
project_info(name)
```
—— 获取项目详情

如果MCP工具不可用，可使用Claude WebSearch/WebFetch作为备选方案。

SearXNG Engine Notes

SearXNG引擎说明

```
engines: "reddit"
```
— PullPush API backend, returns selftext in content
```
site:news.ycombinator.com
```
via Google — HN (native engine broken)
```
site:producthunt.com
```
— Product Hunt launches
```
site:indiehackers.com
```
— Indie Hackers discussions

```
engines: "reddit"
```
—— 基于PullPush API后端，返回内容包含帖子正文
通过Google使用
```
site:news.ycombinator.com
```
—— 搜索HN（原生引擎已损坏）
```
site:producthunt.com
```
—— 搜索ProductHunt发布内容
```
site:indiehackers.com
```
—— 搜索Indie Hackers讨论帖

Steps

操作步骤

Parse project from
```
$ARGUMENTS
```
.
- Read PRD/README to understand: problem, solution, ICP, key features.
- If empty: ask via AskUserQuestion.
Extract search keywords:
- Problem keywords (what users complain about)
- Solution keywords (what users search for)
- Category keywords (the market/niche)
- Competitor names (for "vs" and "alternative" threads)
Search communities (run searches in parallel):

3a. Reddit
For each keyword group, search via MCP
```
web_search(query, engines="reddit")
```
or WebSearch:
- ```
"{problem} reddit"
```
  — pain point threads
- ```
"{solution category} recommendations reddit"
```
  — recommendation requests
- ```
"{competitor} alternative reddit"
```
  — competitor frustration
- ```
"{competitor} vs reddit"
```
  — comparison threads
For each result, extract: subreddit, title, URL, post date, comment count. Filter: prefer threads < 6 months old, > 5 comments (active).

3b. Hacker News
Search via
```
site:news.ycombinator.com
```
:
- ```
"Show HN: {similar product category}"
```
  — similar launches
- ```
"Ask HN: {problem domain}"
```
  — questions in the space
- ```
"{competitor name} site:news.ycombinator.com"
```
  — competitor mentions
Extract: title, URL, points, comment count.

3c. ProductHunt
Search via
```
site:producthunt.com
```
:
- ```
"{product category} site:producthunt.com"
```
  — similar launches
- ```
"{competitor} site:producthunt.com"
```
  — competitor pages
Extract: product names, launch dates, upvote counts, taglines.

3d. Other Communities (optional)
- ```
site:indiehackers.com "{problem}"
```
  — Indie Hackers
- ```
site:dev.to "{solution category}"
```
  — Dev.to (if technical product)
Forced reasoning — outreach strategy: Before drafting, write out:
- Best 5 threads to engage with (highest relevance + activity)
- Tone per community: Reddit (casual, self-deprecating), HN (technical, data-driven), PH (enthusiastic, builder)
- Value-first angle: What genuine help can we offer BEFORE mentioning the product?
- Red lines: No astroturfing, no fake accounts, always disclose you're the builder

Draft responses for top 5 threads:

For each thread:

markdown

### Thread: {title}
**URL:** {url}
**Subreddit/Community:** {community}
**Why relevant:** {1 sentence}

**Draft response:**
{2-4 paragraph response that:
- Directly addresses the question/problem
- Provides genuine value (tips, experience, data)
- Mentions the product naturally (last paragraph)
- Includes "disclaimer: I'm the developer" for transparency
}

Generate ProductHunt launch checklist:

markdown

## ProductHunt Launch Checklist

### Pre-Launch (1 week before)
- [ ] Hunter identified (or self-hunting)
- [ ] Tagline ready (< 60 chars): "{tagline}"
- [ ] Description ready (< 260 chars)
- [ ] 5+ screenshots/GIF prepared
- [ ] Maker comment drafted (story + problem + solution)
- [ ] Launch day scheduled (Tuesday-Thursday, 00:01 PST)

### Launch Day
- [ ] Post live and verified
- [ ] Maker comment posted immediately
- [ ] Share in relevant communities (not vote-begging)
- [ ] Respond to all comments within 1 hour
- [ ] Share progress on Twitter/LinkedIn

### Post-Launch
- [ ] Thank supporters
- [ ] Collect feedback from comments
- [ ] Update product based on feedback

Write outreach plan to

docs/outreach-plan.md

markdown

# Community Outreach Plan: {Project Name}

**Generated:** {YYYY-MM-DD}
**Product:** {one-line description}
**ICP:** {target persona}

## Target Communities

| Community | Relevant Threads Found | Priority |
|-----------|----------------------|----------|
| r/{subreddit} | N | high/medium/low |
| Hacker News | N | high/medium/low |
| ProductHunt | N | high/medium/low |

## Top Threads to Engage

{5 thread drafts from step 5}

## ProductHunt Launch Checklist

{checklist from step 6}

## Search Keywords Used
- {keyword1}: N results
- {keyword2}: N results

---
*Generated by /community-outreach. Review all drafts before posting.*

Output summary — communities found, top 3 threads to engage, PH readiness.

解析项目：从
```
$ARGUMENTS
```
中获取项目信息。
- 阅读PRD/ README文档，理解：问题、解决方案、目标客户群体（ICP）、核心功能。
- 若信息为空：通过AskUserQuestion询问用户。
提取搜索关键词：
- 问题类关键词（用户抱怨的痛点）
- 解决方案类关键词（用户搜索的内容）
- 品类关键词（所属市场/细分领域）
- 竞品名称（用于搜索“对比”和“替代方案”类帖子）
搜索社区（并行执行搜索）：

3a. Reddit
针对每个关键词组，通过MCP
```
web_search(query, engines="reddit")
```
或WebSearch进行搜索：
- ```
"{problem} reddit"
```
  —— 痛点讨论帖
- ```
"{solution category} recommendations reddit"
```
  —— 推荐请求帖
- ```
"{competitor} alternative reddit"
```
  —— 竞品不满帖
- ```
"{competitor} vs reddit"
```
  —— 对比讨论帖
从每个搜索结果中提取：子版块、标题、URL、发布日期、评论数。筛选规则：优先选择发布时间少于6个月、评论数超过5条的活跃帖子。

3b. Hacker News
通过
```
site:news.ycombinator.com
```
进行搜索：
- ```
"Show HN: {similar product category}"
```
  —— 同类产品发布帖
- ```
"Ask HN: {problem domain}"
```
  —— 领域内问题帖
- ```
"{competitor name} site:news.ycombinator.com"
```
  —— 竞品提及帖
提取：标题、URL、点赞数、评论数。

3c. ProductHunt
通过
```
site:producthunt.com
```
进行搜索：
- ```
"{product category} site:producthunt.com"
```
  —— 同类产品发布帖
- ```
"{competitor} site:producthunt.com"
```
  —— 竞品页面
提取：产品名称、发布日期、点赞数、标语。

3d. 其他社区（可选）
- ```
site:indiehackers.com "{problem}"
```
  —— Indie Hackers社区
- ```
site:dev.to "{solution category}"
```
  —— Dev.to社区（若为技术类产品）
强制推导——推广策略：在起草回复前，需明确：
- Top 5高价值帖子：相关性和活跃度最高的5个帖子
- 社区专属语气：Reddit（轻松、自嘲）、HN（技术向、数据驱动）、PH（热情、创业者视角）
- 价值优先角度：在提及产品前，我们能提供哪些真正有帮助的内容？
- 红线规则：禁止虚假造势、禁止使用小号、必须披露自己是产品开发者

为Top 5帖子起草回复：

针对每个帖子，按以下格式撰写：

markdown

### 帖子：{title}
**链接：** {url}
**社区/子版块：** {community}
**相关性说明：** {1句话}

**回复草稿：**
{2-4段回复内容，需包含：
- 直接回应用户的问题/痛点
- 提供真正有价值的内容（技巧、经验、数据）
- 在最后一段自然提及产品
- 包含“免责声明：我是该产品的开发者”以保证透明度
}

生成ProductHunt发布清单：

markdown

## ProductHunt发布清单

### 发布前1周
- [ ] 确定猎人（或自行提交）
- [ ] 准备好标语（≤60字符）："{tagline}"
- [ ] 准备好产品描述（≤260字符）
- [ ] 准备5张以上截图/GIF
- [ ] 起草开发者评论（包含故事、痛点、解决方案）
- [ ] 确定发布日期（周二至周四，太平洋标准时间00:01）

### 发布当日
- [ ] 发布产品并完成验证
- [ ] 立即发布开发者评论
- [ ] 在相关社区分享（严禁求赞）
- [ ] 1小时内回复所有评论
- [ ] 在Twitter/LinkedIn上分享发布进展

### 发布后
- [ ] 感谢支持者
- [ ] 收集评论中的反馈
- [ ] 根据反馈更新产品

将推广计划写入
docs/outreach-plan.md
：

markdown

# 社区推广计划：{Project Name}

**生成日期：** {YYYY-MM-DD}
**产品：** {一句话描述}
**目标客户群体（ICP）：** {目标用户画像}

## 目标社区

| 社区 | 找到的相关帖子数 | 优先级 |
|-----------|----------------------|----------|
| r/{subreddit} | N | 高/中/低 |
| Hacker News | N | 高/中/低 |
| ProductHunt | N | 高/中/低 |

## 重点参与的Top 5帖子

{步骤5中生成的5个回复草稿}

## ProductHunt发布清单

{步骤6中生成的清单}

## 使用的搜索关键词
- {keyword1}: N条结果
- {keyword2}: N条结果

---
*由/community-outreach工具生成。发布前请审核所有回复草稿。*

输出总结——已找到的社区、重点参与的Top 3帖子、ProductHunt发布准备情况。

Critical Rules

核心规则

Value first, product second — every response must genuinely help the person
Always disclose — "I'm the developer" or "disclaimer: I built this"
No vote manipulation — never ask for upvotes
No astroturfing — never pretend to be a user
Respect community rules — check subreddit rules before posting
Quality over quantity — 5 great responses > 50 generic ones

价值优先，产品次之——每一条回复都必须真正帮助用户
必须披露身份——需注明“我是该产品的开发者”或“免责声明：这款产品是我开发的”
禁止操纵投票——绝不要求他人点赞
禁止虚假造势——绝不伪装成普通用户
遵守社区规则——发布前需查看子版块规则
质量重于数量——5条优质回复远胜于50条通用回复

Common Issues

常见问题

SearXNG not available

SearXNG不可用

Cause: SSH tunnel not active or server down. Fix: Run

make search-tunnel

in solopreneur. If still down, skill falls back to Claude WebSearch.

原因： SSH隧道未激活或服务器宕机。 解决方法： 在solopreneur环境中运行

make search-tunnel

。若仍无法使用，工具将自动切换为Claude WebSearch作为备选方案。

No relevant threads found

未找到相关帖子

Cause: Niche too small or wrong keywords. Fix: Broaden search terms. Try competitor names, problem descriptions, or adjacent categories.

原因： 赛道过窄或关键词不当。 解决方法： 扩大搜索词范围。尝试使用竞品名称、痛点描述或相邻品类关键词。

Responses sound promotional

回复听起来过于商业化

Cause: Product mention too prominent or lacks genuine value. Fix: Rewrite with value-first approach: 80% helpful answer, 20% product mention. Always include builder disclosure.

原因： 产品提及过于突兀或缺乏真正有价值的内容。 解决方法： 重写回复，采用价值优先的策略：80%的内容为有帮助的解答，20%的内容提及产品。务必包含开发者身份披露。

solo-community-outreach

Original

Translation

/community-outreach

/社区推广工具

MCP Tools (use if available)

MCP工具（如有可用请使用）

SearXNG Engine Notes

SearXNG引擎说明

Steps

操作步骤

3a. Reddit

3b. Hacker News

3c. ProductHunt

3d. Other Communities (optional)

3a. Reddit

3b. Hacker News

3c. ProductHunt

3d. 其他社区（可选）

Critical Rules

核心规则

Common Issues

常见问题

SearXNG not available

SearXNG不可用

No relevant threads found

未找到相关帖子

Responses sound promotional

回复听起来过于商业化