Agent Skillsshawnpang/startup-founder-skills › community-discovery

community-discovery

GitHub

帮助用户找到目标受众聚集的在线社区(如Slack、Discord、Reddit等),用于有机推广、获取早期用户或建立关系。通过分析平台、评估社区质量并制定参与策略,输出优先级的社区地图和互动计划。

skills/community-discovery/SKILL.md shawnpang/startup-founder-skills

Trigger Scenarios

寻找目标受众所在的社区 询问在哪里进行推广 寻找社区营销渠道 探索分销渠道 寻找Beta测试者或早期采用者

Install

npx skills add shawnpang/startup-founder-skills --skill community-discovery -g -y
More Options

Use without installing

npx skills use shawnpang/startup-founder-skills@community-discovery

指定 Agent (Claude Code)

npx skills add shawnpang/startup-founder-skills --skill community-discovery -a claude-code -g -y

安装 repo 全部 skill

npx skills add shawnpang/startup-founder-skills --all -g -y

预览 repo 内 skill

npx skills add shawnpang/startup-founder-skills --list

SKILL.md

Frontmatter
{
    "name": "community-discovery",
    "reads": [
        "startup-context"
    ],
    "related": [
        "cold-outreach",
        "content-strategy",
        "launch-strategy",
        "landing-page"
    ],
    "description": "When the user wants to find Slack groups, Discord servers, Reddit communities, forums, or online communities where their target audience hangs out. Also use when the user mentions \"where to promote\", \"find communities\", \"community marketing\", or \"distribution channels\"."
}

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.
  2. 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?
  3. 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
  4. 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)
  5. 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:

Platform Best for Promotion approach
Reddit Problem validation, feedback, launch day Answer questions in comments, share in relevant "share your project" threads. Never post direct ads.
Slack B2B relationships, warm intros Be helpful in channels for weeks before mentioning your product. DMs only after building rapport.
Discord Developer communities, gaming, crypto Participate in discussions, share expertise, use #showcase or #self-promo channels if they exist.
Indie Hackers Founder-to-founder, building in public Share your journey with real numbers. The community rewards transparency over polish.
Hacker News Developer/technical audience, launches Show HN for launches. Don't astroturf. Substantive comments build reputation over months.
Facebook Groups SMBs, local businesses, niche B2C Join groups your customers are in. Respond to "looking for recommendations" posts.
LinkedIn Groups Enterprise B2B, professional services Low-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.

Version History

  • 4ad31b4 Current 2026-07-05 10:47

Same Skill Collection

skills/accelerator-application/SKILL.md
skills/architecture-design/SKILL.md
skills/board-update/SKILL.md
skills/churn-analysis/SKILL.md
skills/cicd-setup/SKILL.md
skills/code-review/SKILL.md
skills/cold-outreach/SKILL.md
skills/competitive-analysis/SKILL.md
skills/competitor-monitoring/SKILL.md
skills/content-strategy/SKILL.md
skills/contract-review/SKILL.md
skills/daily-product-digest/SKILL.md
skills/data-room/SKILL.md
skills/earned-media-outreach/SKILL.md
skills/email-marketing/SKILL.md
skills/employer-brand/SKILL.md
skills/event-hosting/SKILL.md
skills/feedback-synthesis/SKILL.md
skills/founder-thought-leadership/SKILL.md
skills/fundraising-email/SKILL.md
skills/interview-kit/SKILL.md
skills/investor-research/SKILL.md
skills/job-description/SKILL.md
skills/landing-page/SKILL.md
skills/launch-strategy/SKILL.md
skills/lead-scoring/SKILL.md
skills/market-research/SKILL.md
skills/mvp-scoping/SKILL.md
skills/onboarding-flow/SKILL.md
skills/partnership-outreach/SKILL.md
skills/pitch-deck/SKILL.md
skills/prd-writing/SKILL.md
skills/privacy-policy/SKILL.md
skills/process-docs/SKILL.md
skills/proposal-generation/SKILL.md
skills/review-mining/SKILL.md
skills/roadmap-planning/SKILL.md
skills/sales-script/SKILL.md
skills/security-review/SKILL.md
skills/sentiment-monitoring/SKILL.md
skills/seo-technical/SKILL.md
skills/soc2-prep/SKILL.md
skills/social-content/SKILL.md
skills/sourcing-outreach/SKILL.md
skills/startup-context/SKILL.md
skills/support-docs/SKILL.md
skills/tech-stack-eval/SKILL.md
skills/terms-of-service/SKILL.md
skills/user-research-synthesis/SKILL.md

Metadata

Files
0
Version
4ad31b4
Hash
afbde436
Indexed
2026-07-05 10:47

Главная - Вики-сайт
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-11 18:15
浙ICP备14020137号-1 $Гость$