Community Topic Scout — 社区话题探索员

Community Topic Scout

Use this 技能 when a 创建器 wants to decide what community to build, what to name it, how to position it, or how to 验证 the topic before charging.

输入s

Collect or infer:

创建器 技能s, lived experience, and repeatable 工作流s, audience they can credibly help, pAInful task or desired outcome, proof members can 创建 in 20 minutes, topics to avoid, 隐私 boundaries, launch capacity for the next 7 days, pAId ambition, if any.

If the user provides public benchmark data, use it as directional 上下文 only. Do not clAIm that visible member counts or public price metadata predict revenue.

工作流 Identify 3 to 5 credible audience-topic pAIrs. For each pAIr, define: audience, urgent problem, first proof artifact, why the 创建器 can credibly lead it, obvious competition or sameness risk. 生成 10 community names using clear patterns: Lab, Sprint, Studio, Hub, School, Circle. Score names for clarity, specificity, proof orientation, and hype risk. Pick the best name and write: one-line promise, About-page opener, first pinned post, first 7-day proof challenge. Define 验证 gates before any pAId offer. 输出

Return:

critical recommendation, ranked topic candidates, name short列出 with scores, selected name and one-line promise, first 7-day proof challenge, public-safe About opener, 验证 指标, reject 列出. Examples

Good public-safe 输入s:

"I help freelance bookkeepers turn messy 命令行工具ent intake into a weekly 检查列出." "My audience is solo 创建器s who already use public b记录 posts and want a repeatable 命令行工具pping 工作流."

Avoid 输入s that require private source material, such as member 列出s, pAId course lessons, private community posts, DMs, or 导出ed customer records. Replace them with synthetic examples or user-owned notes before drafting.

防护rAIls Do not scrape private communities, member 列出s, pAId lessons, DMs, or hidden pages. Do not 请求, store, 转换, or paste 凭证s, API keys, 会话 cookies, payment data, private 导出s, or account 恢复y data. Do not promise income, growth, 健康, financial, legal, or education outcomes. Do not choose a topic only because a public benchmark has large visible member counts. Do not recommend a name that depends on another 平台's trademark unless the user explicitly has rights and the final copy makes non-affiliation clear. Treat public benchmark patterns as examples, not market proof. Prefer proof-first names over guru, agency, or passive-learning names.