Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计提醒

community-discovery社区发现

Agent Skill

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

总安装

703

周安装

29

GitHub Stars

114

下载量

230
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

community-discovery 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

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

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

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 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills