Skip to content
Business
Skill

/community-discovery

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".

BOOST
From plugin
startup-founder-skills
35950 skills
Install
$ npx -y skills add shawnpang/startup-founder-skills --skill community-discovery --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/community-discovery

Context preview

The summary Claude sees to decide when to auto-load this skill.

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".

SKILL.md

community-discovery.SKILL.md
name: community-discovery
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".
related: [cold-outreach, content-strategy, launch-strategy, landing-page]
reads: [startup-context]

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 wee
Read more
Ships withstartup-founder-skills

Hey friends. Shawn here. I've been bootstrapping and starting companies for the past 10 years (still working hard at 996 level).

Get the whole plugin

Other skills on startup-founder-skills.