Token导航 LogoToken导航

Agent Skill · 研究检索

community-discovery(社区发现)

community-discovery 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

community-discovery 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 48,150。

总安装 703周安装 29GitHub Stars 114下载 230核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:community-discovery(社区发现)
来源仓库:https://github.com/shawnpang/startup-founder-skills
仓库路径:skills/community-discovery
安装命令:
npx skills add https://github.com/shawnpang/startup-founder-skills --skill community-discovery
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/shawnpang/startup-founder-skills --skill community-discovery

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

community-discovery 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于创始人寻找目标客户活跃的在线社区,识别有机推广渠道和社区主导增长机会。

可帮助建立社区关系、寻找测试用户或设计合作伙伴,实现除付费广告外的其他分发途径。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/community-discovery

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/shawnpang/startup-founder-skills --skill commu…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

community-discovery 怎么安装?

在终端执行 npx skills add https://github.com/shawnpang/startup-founder-skills --skill community-disco…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

community-discovery 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

community-discovery 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

community-discovery 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

community-discovery 用的人多吗?

公开数据是累计安装 703 次,近一周安装 29 次,下载 230 次,GitHub 114 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

community-discovery 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
community-discovery

社区发现 · 本页

703114只读未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Community Discovery

When to Use

  • Founder wants to find online communities where their target customers are active
  • Founder wants to identify channels for organic promotion and community-led growth
  • Founder wants to build relationships in relevant communities before launching
  • Founder wants to find beta testers, early adopters, or design partners
  • Founder wants distribution beyond paid ads and cold outreach

Context Required

  • Target customer profile (role, industry, interests, seniority)
  • Product category and the problem it solves
  • What the founder wants from communities (feedback, users, partnerships, awareness)
  • Founder's bandwidth for community engagement (lurk and post vs. become a regular)

Workflow

  1. Map the community landscape — identify where your target audience spends time online:

- Reddit: find subreddits by searching for the problem you solve, competitor names, and industry terms. Check subscriber count, post frequency, and moderation rules. - Slack: search Slofile, Slack directories, and Google "[industry] slack community" to find relevant workspaces. - Discord: search Disboard, Discord.me, and Google "[topic] discord server" for relevant servers. - Forums & others: Indie Hackers, Hacker News, Stack Overflow, niche forums, Facebook Groups, LinkedIn Groups.

  1. Qualify each community — not all communities are equal. Score each on:

- Relevance: does your target customer actually hang out here? - Activity: are there regular posts and discussions (not a ghost town)? - Size: big enough to matter, small enough to stand out (sweet spot: 1K-50K members) - Promotion tolerance: does the community allow product mentions, or is it strictly no self-promotion? - Quality of discussion: are conversations substantive or just spam and memes?

  1. Categorize by engagement type — sort communities into:

- Promote: explicitly allows product sharing, launch announcements, or "Show X" posts - Contribute-first: allows organic mentions if you're a genuine, helpful member first - Listen-only: valuable for research and voice-of-customer, but no promotion allowed

  1. Build the engagement plan — for each community:

- Join and observe for 1-2 weeks before posting - Identify the norms (how do regulars communicate? what gets upvoted/praised?) - Plan your first 5 contributions (helpful answers, not product pitches) - Plan when and how to introduce your product (if appropriate)

  1. Create the community map — output a prioritized list with engagement strategy for each.

Output Format

## Community Map for [Product/Category]

### Tier 1 — High Priority (engage weekly)

**[Community Name]** — [Platform]
- Link: [URL]
- Members: [count] | Activity: [posts/day or week]
- Relevance: [why your target customer is here]
- Rules: [promotion policy summary]
- Engagement type: [Promote / Contribute-first / Listen-only]
- Strategy: [specific plan — what to post, how to contribute, when to mention product]
- Key threads/channels: [specific channels or recurring threads to participate in]

### Tier 2 — Medium Priority (engage biweekly)
...

### Tier 3 — Monitor (check monthly)
...

### Engagement Calendar
| Week | Community | Action | Goal |
|------|-----------|--------|------|
| 1 | [name] | Join, read top 20 posts, identify norms | Understand culture |
| 2 | [name] | Answer 3 questions, no product mention | Build reputation |
| 3 | [name] | Share insight related to your space | Establish expertise |
| 4 | [name] | Soft product mention in relevant thread | Drive first traffic |

Frameworks & Best Practices

The 10:1 rule: Give 10 valuable contributions for every 1 product mention. Communities have long memories — one spammy post can get you banned and your brand damaged permanently.

Platform-specific tactics:

PlatformBest forPromotion approach
RedditProblem validation, feedback, launch dayAnswer questions in comments, share in relevant "share your project" threads. Never post direct ads.
SlackB2B relationships, warm introsBe helpful in channels for weeks before mentioning your product. DMs only after building rapport.
DiscordDeveloper communities, gaming, cryptoParticipate in discussions, share expertise, use #showcase or #self-promo channels if they exist.
Indie HackersFounder-to-founder, building in publicShare your journey with real numbers. The community rewards transparency over polish.
Hacker NewsDeveloper/technical audience, launchesShow HN for launches. Don't astroturf. Substantive comments build reputation over months.
Facebook GroupsSMBs, local businesses, niche B2CJoin groups your customers are in. Respond to "looking for recommendations" posts.
LinkedIn GroupsEnterprise B2B, professional servicesLow-signal, high-noise — generally not worth the effort unless very niche.

Red flags — avoid these communities:

  • More self-promo than real discussion
  • Moderators are inactive or absent
  • "Pay to post" or "pay for featured" requirements
  • Last meaningful discussion was months ago
  • Members are mostly other founders/marketers (not your actual customers)

Common mistakes:

  • Joining 20 communities and being active in none (pick 3-5 and go deep)
  • Leading with your product instead of being helpful first
  • Copy-pasting the same message across communities
  • Ignoring community rules and getting banned
  • Giving up after 2 weeks because no one clicked your link

Related Skills

  • cold-outreach — for direct outreach to individuals found through communities
  • content-strategy — for creating content to share in communities
  • launch-strategy — for using communities as launch distribution channels
  • landing-page — to convert community traffic into signups

Examples

Prompt: "I'm building a tool for data engineers. Where should I be hanging out online?"

Good output includes: A prioritized map of communities — specific subreddits (r/dataengineering, r/apachekafka), Slack groups (dbt Slack, Data Engineering Weekly), Discord servers, relevant HN threads, and a 4-week engagement plan for the top 3.

Prompt: "We're launching our design tool next month. Which communities should I warm up in advance?"

Good output includes: Communities sorted by launch relevance (Designer Hangout Slack, r/UI_Design, Dribbble, specific Discord servers), a pre-launch engagement timeline, and specific "Show X" or "Share your project" threads to target on launch day.

平台分布

Codex

37.98%
按下载量换算87

Claude

26.56%
按下载量换算61

Cursor

19.21%
按下载量换算44

Gemini CLI

8.97%
按下载量换算21

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills