community-builder
npx machina-cli add skill ncklrs/startup-os-skills/community-builder --openclawCommunity Builder
Expert guidance for building, growing, and nurturing thriving online communities — from platform selection to engagement programs to community-led growth strategies.
Philosophy
Great communities are built on three pillars:
- Shared purpose — Members need a reason bigger than the product
- Genuine connection — People stay for people, not features
- Member empowerment — The best communities run themselves
How This Skill Works
When invoked, apply the guidelines in rules/ organized by:
strategy-*— Community-led growth, positioning, and strategic planningplatform-*— Discord, Slack, Circle, and platform selectiononboarding-*— Member welcome flows and activationengagement-*— Programs, rituals, and recurring activitiescontent-*— User-generated content and content programsprograms-*— Ambassador, champion, and super-user programsmetrics-*— Community health and analyticsmoderation-*— Governance, moderation, and conflict resolutiondevrel-*— Developer relations and technical community building
Core Frameworks
The Community Flywheel
┌─────────────────────────────────────────────────────────────┐
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ ATTRACT │───▶│ ACTIVATE │───▶│ ENGAGE │ │
│ │ (Reach) │ │ (Value) │ │ (Habit) │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ ▲ │ │
│ │ ┌──────────┐ │ │
│ │ │ ADVOCATE │ │ │
│ └──────────│ (Amplify)│◀─────────┘ │
│ └──────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
Community Maturity Model
| Stage | Characteristics | Focus |
|---|---|---|
| Nascent | Founder-led, <100 members | 1:1 conversations, manual everything |
| Growing | Early champions emerge, 100-1,000 | Systems, rituals, first programs |
| Scaling | Self-sustaining activity, 1,000-10,000 | Governance, moderation, delegation |
| Mature | Community-led initiatives, 10,000+ | Platform, sub-communities, ecosystem |
Member Journey Stages
| Stage | Goal | Key Metric |
|---|---|---|
| Lurker | First interaction | Post/reply count |
| Newcomer | Find value, connect | Retention D7 |
| Regular | Form habits, contribute | Weekly active |
| Champion | Lead initiatives | Content created |
| Ambassador | Represent externally | Referrals, reach |
The 1-9-90 Rule
In most communities:
- 1% create content (Creators)
- 9% engage with content (Contributors)
- 90% consume content (Lurkers)
Goal: Move people up the engagement ladder, not force everyone to create.
Community vs Audience
| Dimension | Audience | Community |
|---|---|---|
| Direction | One to many | Many to many |
| Value | From creator | From each other |
| Ownership | Creator owns | Members co-own |
| Content | Creator produces | Members produce |
| Retention | Content-dependent | Relationship-dependent |
| Scalability | Linear | Network effects |
Platform Comparison at a Glance
| Platform | Best For | Key Strength | Key Weakness |
|---|---|---|---|
| Discord | Gaming, dev, real-time | Rich features, free | Overwhelming UX |
| Slack | Professional, B2B | Familiar, searchable | Expensive at scale |
| Circle | Courses, creators | Clean UX, courses | Less real-time |
| Discourse | Long-form, async | SEO, knowledge base | Old-school feel |
| GitHub Discussions | Open source, devs | Code integration | Limited features |
| Public discovery | SEO, scale | Less control |
Key Metrics Overview
| Category | Metrics |
|---|---|
| Growth | New members, referral rate, churn rate |
| Engagement | DAU/MAU, posts per member, response time |
| Health | Sentiment, helpful answers, retention |
| Value | NPS, support deflection, product influence |
Community-Led Growth (CLG) Quick Reference
| Motion | Description | Best For |
|---|---|---|
| Community-Assisted | Community supports product users | Support deflection |
| Community-Qualified | Leads emerge from community | B2B, enterprise |
| Community-Distributed | Growth through member networks | Viral products |
| Community-Created | Members build on platform | Platforms, APIs |
Engagement Program Types
| Program | Frequency | Goal |
|---|---|---|
| Office Hours | Weekly | Direct access, Q&A |
| Show & Tell | Weekly/Monthly | Member showcases |
| AMAs | Monthly | Expert access |
| Challenges | Monthly/Quarterly | Activation, content |
| Conferences | Annual | Milestone, celebration |
Anti-Patterns
- Build it and they will come — Communities require constant nurturing, especially early
- Metrics over meaning — Vanity metrics don't equal healthy community
- Over-engineering early — Start simple, add complexity as needed
- Ignoring lurkers — 90% of your community provides value by consuming
- Founder absence — Early communities need visible leadership
- Feature obsession — People join for people, not features
- Forced engagement — Authentic connection beats gamification
- One-size-fits-all — Different member types need different experiences
- Scaling too fast — Growth without engagement destroys community
- Neglecting moderation — One bad actor can poison the well
Source
git clone https://github.com/ncklrs/startup-os-skills/blob/main/skills/community-builder/SKILL.mdView on GitHub Overview
Community-builder provides expert guidance for building, growing, and nurturing thriving online communities—from platform selection to engagement programs and community-led growth strategies. It emphasizes shared purpose, genuine connection, and member empowerment as core pillars. Use this skill to design onboarding, run ambassador programs, measure health, and implement DevRel strategies.
How This Skill Works
When invoked, apply the guidelines organized under rules/ by category: strategy- for growth and planning, platform- for tool selection, onboarding- for welcome flows, engagement- for programs and rituals, content- for UGC, programs- for ambassador initiatives, metrics- for health analytics, moderation- for governance, and devrel- for developer relations. Core frameworks include The Community Flywheel, the Community Maturity Model, Member Journey Stages, the 1-9-90 Rule, and platform comparisons to guide decisions.
When to Use It
- Building a developer or online community from scratch (platform selection, onboarding, and engagement design)
- Scaling activation and recurring engagement with rituals, content programs, and governance
- Designing ambassador/super-user programs to amplify reach and advocacy
- Measuring community health, moderation systems, and DevRel effectiveness
- Setting up governance, moderation, and member-owned initiatives across platforms
Quick Start
- Step 1: Define the community's shared purpose and target member personas
- Step 2: Choose platforms and map onboarding, activation, and engagement rituals
- Step 3: Design governance, moderation, and ambassador programs with clear metrics
Best Practices
- Define shared purpose and member value early
- Establish onboarding flows that activate newcomers quickly
- Design rituals, programs, and content that encourage participation
- Implement clear moderation and governance with escalation paths
- Measure health using maturity stages and flywheel progress
Example Use Cases
- Open-source developer community on Discord with an ambassador program and governance
- SaaS product Slack community with onboarding flows, UGC programs, and monthly rituals
- Community health dashboard tracking Flywheel metrics and maturity stage transitions
- Circle-based onboarding and engagement playbooks for new members
- Community-led product feedback loop driving roadmap and governance decisions