mcpField
C
community-building

community-building

github.com/jonathimerMarketing & growth87109 installsUpdated 35w ago
Repository

About community-building

A community-building guide for people managing developer communities across Discord, Slack, forums, and other platforms. It spans platform selection and onboarding through engagement, moderation, automation, and community metrics.

Key features

  1. 01Framework for choosing a community platform
  2. 02Channel structures and member onboarding
  3. 03Engagement programs and member recognition
  4. 04Conduct guidelines and moderation practices
  5. 05Community growth and health metrics
  6. 06Bot and operations automation ideas

Use cases

  1. 01Select a platform for a developer community
  2. 02Design Discord or Slack channels and onboarding
  3. 03Plan discussions, events, and contributor recognition
  4. 04Set moderation practices and track community health

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jonathimer/devmarketing-skills --skill community-building

After installing, type/community-buildingin Claude Code to confirm it loaded.

Bundled filesREADME.md

Details

From the project README

Community Building

This skill helps you build and manage developer communities on Discord, Slack, forums, and other platforms. Covers channel structure, onboarding, engagement programs, handling toxicity, and community-led growth.


Before You Start

Load your audience context first. Read .agents/developer-audience-context.md to understand:

  • Who your developers are (role, seniority, interests)
  • Where they already hang out (to avoid competing platforms)
  • What problems they discuss (community topic focus)
  • How they communicate (formal vs. casual tone)

If the context file doesn't exist, run the developer-audience-context skill first.


Platform Selection

Comparison Matrix
PlatformBest ForProsCons
DiscordDeveloper tools, gaming, OSSReal-time, rich features, freeCan be chaotic, less enterprise
SlackEnterprise, B2B SaaSProfessional, familiarExpensive at scale, message limits
GitHub DiscussionsOSS projectsIntegrated, async, searchableLess community feel
DiscourseLong-form, searchableSEO, threading, ownershipMaintenance, hosting costs
CircleCourses, paid communitiesCourses integration, cleanPaid, less developer-native
Decision Framework
If your audience is...Consider
Individual developers, OSSDiscord
Enterprise teamsSlack
Technical, async-preferredGitHub Discussions
Mixed, need searchabilityDiscourse
Course/education basedCircle

Channel Structure

Discord Channel Template
📢 INFORMATION
├── #welcome — First landing, rules, links
├── #announcements — Official updates (admin-only posting)
├── #rules — Code of conduct
└── #introductions — New member intros

💬 GENERAL
├── #general — Main discussion
├── #off-topic — Non-project chat
└── #show-what-you-built — Share projects

❓ SUPPORT
├── #help — General questions
├── #troubleshooting — Bug help
└── #feature-requests — Suggestions

🔧 TECHNICAL
├── #backend — Backend discussions
├── #frontend — Frontend discussions
└── #devops — Infrastructure discussions

🤝 COMMUNITY
├── #jobs — Job postings (if allowed)
├── #events — Meetups, conferences
└── #content — Blog posts, videos

📚 RESOURCES
├── #learning — Tutorials, courses
└── #tools — Useful tools and libraries
Slack Channel Template
# welcome
# announcements (admin-only)
# general
# help
# random (off-topic)
# jobs (optional)
# introductions
# feedback
Channel Guidelines
Channel TypePosting RulesModeration Level
AnnouncementsAdmin onlyN/A
GeneralOn-topic discussionLight
HelpQuestions welcome, be patientMedium
Off-topicAnything goes (within CoC)Light
JobsStructured format requiredHeavy
IntroductionsOne post per personLight

Onboarding Experience

New Member Journey
Join Server
    ↓
Welcome Message (DM or public)
    ↓
Read Rules / Accept
    ↓
Verify (optional: GitHub, email)
    ↓
Introduce Yourself
    ↓
First Interaction
    ↓
Regular Member
Welcome Message Template

Discord DM:

Welcome to [Community Name]! 👋

Here's how to get started:

1. Read the rules in #rules
2. Introduce yourself in #introductions
3. Ask questions in #help — we're friendly!

Quick links:
• Documentation: [link]
• Getting started: [link]
• GitHub: [link]

We're glad you're here!

Public #welcome channel:

# Welcome to [Community Name]!

We're [brief description of who you are and what you do].

## Quick Start

1. **Read the rules** → #rules
2. **Introduce yourself** → #introductions
3. **Get help** → #help
4. **Chat with us** → #general

## Useful Links

- [Documentation]
- [GitHub]
- [Website]

## Questions?

Drop a message in #help or mention @moderators
Role Assignment
RoleHow to GetPermissions
New MemberAuto on joinLimited channels
MemberVerify or time-basedFull access
ContributorPR merged, active helperBadge, special channel
ModeratorInvitedModeration powers
AdminCore teamFull access

Engagement Programs

Discussion Prompts

Schedule regular engagement:

DayPrompt TypeExample
MondayThis week's goals"What are you working on this week?"
WednesdayTechnical question"Controversial: Tabs or spaces?"
FridayShow & Tell"Share what you shipped this week"
Recognition Programs
ProgramDescriptionFrequency
Contributor of the MonthRecognize top helpersMonthly
First PR CelebrationWelcome new contributorsAs happens
Milestone Badges10/50/100 messagesAutomatic
Expert RolesDomain expertise recognitionQuarterly
Event Ideas
Event TypeFormatEffort
Office HoursLive Q&A with teamLow
Show & TellMembers demo projectsLow
WorkshopsTeaching sessionsMedium
HackathonsBuild challengesHigh
Game NightNon-tech funLow
AMA SessionsGuest expertsMedium
Engagement Metrics
MetricWhat It Tells You
DAU/MAUDaily vs monthly active users
Messages per userIndividual engagement depth
Questions answeredCommunity self-sufficiency
New member retentionOnboarding effectiveness
Event attendanceProgram resonance

Handling Toxicity

Code of Conduct Essentials
# Code of Conduct

## Our Standards

**Do:**
- Be respectful and inclusive
- Help others learn (no "RTFM")
- Assume good intentions
- Give constructive feedback
- Report problems, don't engage

**Don't:**
- Personal attacks or harassment
- Discrimination of any kind
- Spam or self-promotion
- NSFW content
- Doxxing or privacy violations
- Bad faith arguments

## Enforcement

1. **Warning** — First offense, good faith
2. **Temp mute** — Repeated issues
3. **Temp ban** — Serious violations
4. **Permanent ban** — Egregious or repeated

## Reporting

DM any @moderator or use the report feature.
All reports are confidential.
Moderation Playbook
SituationResponse
Heated debate"Let's keep this constructive. Both perspectives have merit."
Help vampire"Here's a guide on asking good questions: [link]"
Self-promotion spamDelete, warn, or ban depending on frequency
Off-topic drift"Great discussion! Let's move this to #off-topic"
HarassmentImmediate mute, investigate, likely ban
Bad faith trollDon't engage publicly, ban quietly
De-escalation Techniques
  1. Acknowledge feelings — "I can see this is frustrating"
  2. Move to DM — "Let's continue this privately"
  3. Take a break — "Let's pause and revisit tomorrow"
  4. Clarify intent — "I think there might be a misunderstanding"
  5. Set boundaries — "We're here to help, but not to be yelled at"
Moderator Self-Care
RiskMitigation
BurnoutRotate moderator duties
Taking it personallyRemember: it's not about you
Imposter syndromeRegular team check-ins
IsolationModerator private channel

Community-Led Growth

Word-of-Mouth Tactics
TacticHow
Referral programRewards for invites that stick
Share-worthy contentExclusive insights, early access
Member spotlightsFeature members → they share
Success stories"I got a job through this community"
User-Generated Content
Content TypeHow to Encourage
Tutorials"Share your setup in #show-what-you-built"
Q&A threadsReward helpful answers
Project showcasesMonthly demo events
TestimonialsAsk happy members
Community Champions

Identify and empower super-users:

Champion TypeRole
GreetersWelcome new members
HelpersAnswer support questions
Content creatorsTutorials, videos, guides
Event organizersRun community events
ConnectorsIntroduce people to each other

Community Metrics

Health Dashboard
MetricHealthyWarningAction Needed
Response time (support)<24h24-72h>72h
Unanswered questions<10%10-25%>25%
New member 7-day retention>40%20-40%<20%
Monthly active ratio>20%10-20%<10%
Moderator messages ratio<30%30-50%>50%
Growth Metrics
MetricHow to Track
Total membersPlatform analytics
Join rateNew members per week
Churn rateLeaves per month
Engagement depthMessages per active user
Support success% questions resolved

Automation

Useful Bots (Discord)
BotPurpose
MEE6 / Carl-botModeration, welcome messages, roles
StatbotAnalytics and metrics
Ticket ToolSupport ticket system
GitHub BotRepo activity notifications
YAGPDBAdvanced moderation, custom commands
Automation Ideas
AutomationBenefit
Welcome DMConsistent onboarding
Auto-role on joinImmediate access
Inactive member pingRe-engagement
Support ticket creationOrganized help
GitHub notificationsKeep community informed
Scheduled postsRegular engagement

Tools

ToolUse Case
OctolensMonitor community mentions across GitHub, Twitter, Reddit. Find where your community members talk about you. Track sentiment. Discover community content to amplify.
CommsorCommunity operations platform
NotionCommunity wiki and resources
LumaEvent management
StreamYard/RestreamLive event streaming

Related Skills

  • developer-audience-context — Know your community members
  • open-source-marketing — OSS community building
  • developer-advocacy — Personal brand in community
  • developer-newsletter — Community digest content

Comments

Markdown supported