Skills/Community Launch/SKILL.md
When the user wants to launch a new community from scratch, plan a community launch, or relaunch an existing community. Also use when the user mentions 'launch community,' 'start a community,' 'build a community,' 'community from scratch,' 'relaunch,' or 'community kickoff.' For overall strategy, see community-strategy. For growth after launch, see community-growth.
npx skillsauth add studio-self/tribalism community-launchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert at launching communities that build momentum from day one. Your goal is to help users avoid the empty-room problem and create a community that feels alive from the first week.
Check for community context first:
If .claude/community-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
The #1 reason communities fail at launch: they open the doors before there's anyone inside. Nobody wants to be the first person in an empty room.
The solution: Never launch to the public until your community already looks active.
The data: 80% of communities that launch publicly without pre-seeded activity die within 3 months (CMX research). Communities that launch with 30+ active founding members have 3x higher 6-month survival rates. Indie Hackers launched with 50 hand-picked founders and hit 100K members in 18 months. Morning Brew's referral community grew to 1.5M subscribers by launching with 1,000 hand-recruited college ambassadors.
You need 20-50 founding members committed before you open. These are not random signups — they're hand-picked.
Where to find them:
How to recruit: Send personal messages (not mass emails). The pitch:
Hey [name],
I'm building [community name] — a [type] for [audience] focused on [topic].
I'm putting together a founding group of [X] people before we open to the public.
Given your [background/interest/work on X], I think you'd be a great fit.
As a founder, you'd help shape what this becomes — the culture, the topics,
the direction. Plus [specific benefit: early access, direct line to team, etc.].
Interested?
Aim for 60% acceptance rate. If lower, your pitch or targeting needs work. Product Hunt's community started with personal emails from Ryan Hoover to 100 tech influencers — 70%+ acceptance rate because the invite felt exclusive and personal. Superpath (content marketing community) recruited 200 founding members through personal LinkedIn DMs, hitting a 55% acceptance rate.
Before inviting anyone:
Starter channel structure:
#welcome — Introductions and orientation
#general — Main discussion
#[topic-1] — Primary topic channel
#[topic-2] — Secondary topic channel
#feedback — Suggestions for the community itself
Plan a specific event or activity for launch week that gives people a reason to show up at the same time:
If you want to build anticipation before launch:
For communities that have gone quiet and need a reset:
| Metric | Target | Excellent | |--------|--------|-----------| | Founding member acceptance rate | 50-60% | 70%+ | | Day 1 activation (founding members who post) | 60% | 80%+ | | Week 1 retention | 70% | 85%+ | | Member-invited growth (week 1) | 1.5x founding base | 2-3x | | Time to first 100 members | 2-4 weeks | <2 weeks | | Organic discussions per day (week 2+) | 2-3 | 5+ |
| Mistake | Fix | |---------|-----| | Opening to everyone on day 1 | Start with founding members only | | Creating too many channels | Start with 3-5, expand based on demand | | No programming or events | Plan at least one launch week event | | Waiting for perfection | Launch when it's good enough, iterate | | Not being present enough | Plan to be highly active the first 2 weeks | | Mass invite blast | Personal invitations to hand-picked people | | No clear first action for new members | Pin clear "do this first" instructions |
development
When the user wants to reduce community churn, re-engage inactive members, or improve member retention. Also use when the user mentions 'retention,' 'churn,' 'inactive members,' 'win-back,' 're-engagement,' 'community churn,' 'member drop-off,' or 'ghost members.' For onboarding new members, see member-onboarding. For engagement programs, see engagement-programs.
tools
When the user wants to choose a community platform, compare community tools, or migrate between platforms. Also use when the user mentions 'Discord,' 'Slack,' 'Circle,' 'forum,' 'community platform,' 'where to host,' 'platform comparison,' 'migrate community,' or 'which platform.' For setting up the chosen platform, see community-ops.
development
When the user wants to create community guidelines, set up moderation workflows, handle conflict, or design governance structures. Also use when the user mentions 'moderation,' 'community rules,' 'guidelines,' 'code of conduct,' 'conflict resolution,' 'toxic members,' 'trust and safety,' 'banning,' or 'governance.' For crisis situations, see crisis-management.
development
When the user wants to design or improve the new member experience, reduce early churn, or increase activation rates. Also use when the user mentions 'onboarding,' 'new member experience,' 'welcome flow,' 'first day experience,' 'member activation,' or 'new member churn.' For ongoing engagement, see engagement-programs. For overall strategy, see community-strategy.