Community Building
When to Use
Use this skill when you need when the user wants to build, grow, or improve a developer community on Discord, Slack, or forums. Trigger phrases include "developer community," "Discord server," "Slack community," "community strategy," "community engagement," "community moderation," "community growth," or "community...
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
| Platform |
Best For |
Pros |
Cons |
| Discord |
Developer tools, gaming, OSS |
Real-time, rich features, free |
Can be chaotic, less enterprise |
| Slack |
Enterprise, B2B SaaS |
Professional, familiar |
Expensive at scale, message limits |
| GitHub Discussions |
OSS projects |
Integrated, async, searchable |
Less community feel |
| Discourse |
Long-form, searchable |
SEO, threading, ownership |
Maintenance, hosting costs |
| Circle |
Courses, paid communities |
Courses integration, clean |
Paid, less developer-native |
Decision Framework
| If your audience is... |
Consider |
| Individual developers, OSS |
Discord |
| Enterprise teams |
Slack |
| Technical, async-preferred |
GitHub Discussions |
| Mixed, need searchability |
Discourse |
| Course/education based |
Circle |
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 Type |
Posting Rules |
Moderation Level |
| Announcements |
Admin only |
N/A |
| General |
On-topic discussion |
Light |
| Help |
Questions welcome, be patient |
Medium |
| Off-topic |
Anything goes (within CoC) |
Light |
| Jobs |
Structured format required |
Heavy |
| Introductions |
One post per person |
Light |
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
| Role |
How to Get |
Permissions |
| New Member |
Auto on join |
Limited channels |
| Member |
Verify or time-based |
Full access |
| Contributor |
PR merged, active helper |
Badge, special channel |
| Moderator |
Invited |
Moderation powers |
| Admin |
Core team |
Full access |
Engagement Programs
Discussion Prompts
Schedule regular engagement:
| Day |
Prompt Type |
Example |
| Monday |
This week's goals |
"What are you working on this week?" |
| Wednesday |
Technical question |
"Controversial: Tabs or spaces?" |
| Friday |
Show & Tell |
"Share what you shipped this week" |
Recognition Programs
| Program |
Description |
Frequency |
| Contributor of the Month |
Recognize top helpers |
Monthly |
| First PR Celebration |
Welcome new contributors |
As happens |
| Milestone Badges |
10/50/100 messages |
Automatic |
| Expert Roles |
Domain expertise recognition |
Quarterly |
Event Ideas
| Event Type |
Format |
Effort |
| Office Hours |
Live Q&A with team |
Low |
| Show & Tell |
Members demo projects |
Low |
| Workshops |
Teaching sessions |
Medium |
| Hackathons |
Build challenges |
High |
| Game Night |
Non-tech fun |
Low |
| AMA Sessions |
Guest experts |
Medium |
Engagement Metrics
| Metric |
What It Tells You |
| DAU/MAU |
Daily vs monthly active users |
| Messages per user |
Individual engagement depth |
| Questions answered |
Community self-sufficiency |
| New member retention |
Onboarding effectiveness |
| Event attendance |
Program 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
| Situation |
Response |
| Heated debate |
"Let's keep this constructive. Both perspectives have merit." |
| Help vampire |
"Here's a guide on asking good questions: [link]" |
| Self-promotion spam |
Delete, warn, or ban depending on frequency |
| Off-topic drift |
"Great discussion! Let's move this to #off-topic" |
| Harassment |
Immediate mute, investigate, likely ban |
| Bad faith troll |
Don't engage publicly, ban quietly |
De-escalation Techniques
- Acknowledge feelings — "I can see this is frustrating"
- Move to DM — "Let's continue this privately"
- Take a break — "Let's pause and revisit tomorrow"
- Clarify intent — "I think there might be a misunderstanding"
- Set boundaries — "We're here to help, but not to be yelled at"
Moderator Self-Care
| Risk |
Mitigation |
| Burnout |
Rotate moderator duties |
| Taking it personally |
Remember: it's not about you |
| Imposter syndrome |
Regular team check-ins |
| Isolation |
Moderator private channel |
Community-Led Growth
Word-of-Mouth Tactics
| Tactic |
How |
| Referral program |
Rewards for invites that stick |
| Share-worthy content |
Exclusive insights, early access |
| Member spotlights |
Feature members → they share |
| Success stories |
"I got a job through this community" |
User-Generated Content
| Content Type |
How to Encourage |
| Tutorials |
"Share your setup in #show-what-you-built" |
| Q&A threads |
Reward helpful answers |
| Project showcases |
Monthly demo events |
| Testimonials |
Ask happy members |
Community Champions
Identify and empower super-users:
| Champion Type |
Role |
| Greeters |
Welcome new members |
| Helpers |
Answer support questions |
| Content creators |
Tutorials, videos, guides |
| Event organizers |
Run community events |
| Connectors |
Introduce people to each other |
Community Metrics
Health Dashboard
| Metric |
Healthy |
Warning |
Action Needed |
| Response time (support) |
<24h |
24-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
| Metric |
How to Track |
| Total members |
Platform analytics |
| Join rate |
New members per week |
| Churn rate |
Leaves per month |
| Engagement depth |
Messages per active user |
| Support success |
% questions resolved |
Automation
Useful Bots (Discord)
| Bot |
Purpose |
| MEE6 / Carl-bot |
Moderation, welcome messages, roles |
| Statbot |
Analytics and metrics |
| Ticket Tool |
Support ticket system |
| GitHub Bot |
Repo activity notifications |
| YAGPDB |
Advanced moderation, custom commands |
Automation Ideas
| Automation |
Benefit |
| Welcome DM |
Consistent onboarding |
| Auto-role on join |
Immediate access |
| Inactive member ping |
Re-engagement |
| Support ticket creation |
Organized help |
| GitHub notifications |
Keep community informed |
| Scheduled posts |
Regular engagement |
Tools
| Tool |
Use Case |
| Octolens |
Monitor community mentions across GitHub, Twitter, Reddit. Find where your community members talk about you. Track sentiment. Discover community content to amplify. |
| Commsor |
Community operations platform |
| Notion |
Community wiki and resources |
| Luma |
Event management |
| StreamYard/Restream |
Live 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
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
1---2name: community-building3description: When the user wants to build, grow, or improve a developer community on Discord, Slack, or forums.4license: MIT5---6
7# Community Building
8## When to Use
9
10Use this skill when you need when the user wants to build, grow, or improve a developer community on Discord, Slack, or forums. Trigger phrases include "developer community," "Discord server," "Slack community," "community strategy," "community engagement," "community moderation," "community growth," or "community...
11
12
13This 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.
14
15---
16
17## Before You Start
18
19**Load your audience context first.** Read `.agents/developer-audience-context.md` to understand:
20
21- Who your developers are (role, seniority, interests)
22- Where they already hang out (to avoid competing platforms)
23- What problems they discuss (community topic focus)
24- How they communicate (formal vs. casual tone)
25
26If the context file doesn't exist, run the `developer-audience-context` skill first.
27
28---
29
30## Platform Selection
31
32### Comparison Matrix
33
34| Platform | Best For | Pros | Cons |
35|----------|----------|------|------|
36| **Discord** | Developer tools, gaming, OSS | Real-time, rich features, free | Can be chaotic, less enterprise |
37| **Slack** | Enterprise, B2B SaaS | Professional, familiar | Expensive at scale, message limits |
38| **GitHub Discussions** | OSS projects | Integrated, async, searchable | Less community feel |
39| **Discourse** | Long-form, searchable | SEO, threading, ownership | Maintenance, hosting costs |
40| **Circle** | Courses, paid communities | Courses integration, clean | Paid, less developer-native |
41
42### Decision Framework
43
44| If your audience is... | Consider |
45|------------------------|----------|
46| Individual developers, OSS | Discord |
47| Enterprise teams | Slack |
48| Technical, async-preferred | GitHub Discussions |
49| Mixed, need searchability | Discourse |
50| Course/education based | Circle |
51
52---
53
54## Channel Structure
55
56### Discord Channel Template
57
58```
59📢 INFORMATION
60├── #welcome — First landing, rules, links
61├── #announcements — Official updates (admin-only posting)
62├── #rules — Code of conduct
63└── #introductions — New member intros
64
65💬 GENERAL
66├── #general — Main discussion
67├── #off-topic — Non-project chat
68└── #show-what-you-built — Share projects
69
70❓ SUPPORT
71├── #help — General questions
72├── #troubleshooting — Bug help
73└── #feature-requests — Suggestions
74
75🔧 TECHNICAL
76├── #backend — Backend discussions
77├── #frontend — Frontend discussions
78└── #devops — Infrastructure discussions
79
80🤝 COMMUNITY
81├── #jobs — Job postings (if allowed)
82├── #events — Meetups, conferences
83└── #content — Blog posts, videos
84
85📚 RESOURCES
86├── #learning — Tutorials, courses
87└── #tools — Useful tools and libraries
88```
89
90### Slack Channel Template
91
92```
93# welcome
94# announcements (admin-only)
95# general
96# help
97# random (off-topic)
98# jobs (optional)
99# introductions
100# feedback
101```
102
103### Channel Guidelines
104
105| Channel Type | Posting Rules | Moderation Level |
106|--------------|---------------|------------------|
107| **Announcements** | Admin only | N/A |
108| **General** | On-topic discussion | Light |
109| **Help** | Questions welcome, be patient | Medium |
110| **Off-topic** | Anything goes (within CoC) | Light |
111| **Jobs** | Structured format required | Heavy |
112| **Introductions** | One post per person | Light |
113
114---
115
116## Onboarding Experience
117
118### New Member Journey
119
120```
121Join Server
122 ↓
123Welcome Message (DM or public)
124 ↓
125Read Rules / Accept
126 ↓
127Verify (optional: GitHub, email)
128 ↓
129Introduce Yourself
130 ↓
131First Interaction
132 ↓
133Regular Member
134```
135
136### Welcome Message Template
137
138**Discord DM:**
139```
140Welcome to [Community Name]! 👋
141
142Here's how to get started:
143
1441. Read the rules in #rules
1452. Introduce yourself in #introductions
1463. Ask questions in #help — we're friendly!
147
148Quick links:
149• Documentation: [link]
150• Getting started: [link]
151• GitHub: [link]
152
153We're glad you're here!
154```
155
156**Public #welcome channel:**
157```
158# Welcome to [Community Name]!
159
160We're [brief description of who you are and what you do].
161
162## Quick Start
163
1641. **Read the rules** → #rules
1652. **Introduce yourself** → #introductions
1663. **Get help** → #help
1674. **Chat with us** → #general
168
169## Useful Links
170
171- [Documentation]
172- [GitHub]
173- [Website]
174
175## Questions?
176
177Drop a message in #help or mention @moderators
178```
179
180### Role Assignment
181
182| Role | How to Get | Permissions |
183|------|------------|-------------|
184| **New Member** | Auto on join | Limited channels |
185| **Member** | Verify or time-based | Full access |
186| **Contributor** | PR merged, active helper | Badge, special channel |
187| **Moderator** | Invited | Moderation powers |
188| **Admin** | Core team | Full access |
189
190---
191
192## Engagement Programs
193
194### Discussion Prompts
195
196Schedule regular engagement:
197
198| Day | Prompt Type | Example |
199|-----|-------------|---------|
200| Monday | This week's goals | "What are you working on this week?" |
201| Wednesday | Technical question | "Controversial: Tabs or spaces?" |
202| Friday | Show & Tell | "Share what you shipped this week" |
203
204### Recognition Programs
205
206| Program | Description | Frequency |
207|---------|-------------|-----------|
208| **Contributor of the Month** | Recognize top helpers | Monthly |
209| **First PR Celebration** | Welcome new contributors | As happens |
210| **Milestone Badges** | 10/50/100 messages | Automatic |
211| **Expert Roles** | Domain expertise recognition | Quarterly |
212
213### Event Ideas
214
215| Event Type | Format | Effort |
216|------------|--------|--------|
217| **Office Hours** | Live Q&A with team | Low |
218| **Show & Tell** | Members demo projects | Low |
219| **Workshops** | Teaching sessions | Medium |
220| **Hackathons** | Build challenges | High |
221| **Game Night** | Non-tech fun | Low |
222| **AMA Sessions** | Guest experts | Medium |
223
224### Engagement Metrics
225
226| Metric | What It Tells You |
227|--------|------------------|
228| **DAU/MAU** | Daily vs monthly active users |
229| **Messages per user** | Individual engagement depth |
230| **Questions answered** | Community self-sufficiency |
231| **New member retention** | Onboarding effectiveness |
232| **Event attendance** | Program resonance |
233
234---
235
236## Handling Toxicity
237
238### Code of Conduct Essentials
239
240```markdown
241# Code of Conduct
242
243## Our Standards
244
245**Do:**
246- Be respectful and inclusive
247- Help others learn (no "RTFM")
248- Assume good intentions
249- Give constructive feedback
250- Report problems, don't engage
251
252**Don't:**
253- Personal attacks or harassment
254- Discrimination of any kind
255- Spam or self-promotion
256- NSFW content
257- Doxxing or privacy violations
258- Bad faith arguments
259
260## Enforcement
261
2621. **Warning** — First offense, good faith
2632. **Temp mute** — Repeated issues
2643. **Temp ban** — Serious violations
2654. **Permanent ban** — Egregious or repeated
266
267## Reporting
268
269DM any @moderator or use the report feature.
270All reports are confidential.
271```
272
273### Moderation Playbook
274
275| Situation | Response |
276|-----------|----------|
277| **Heated debate** | "Let's keep this constructive. Both perspectives have merit." |
278| **Help vampire** | "Here's a guide on asking good questions: [link]" |
279| **Self-promotion spam** | Delete, warn, or ban depending on frequency |
280| **Off-topic drift** | "Great discussion! Let's move this to #off-topic" |
281| **Harassment** | Immediate mute, investigate, likely ban |
282| **Bad faith troll** | Don't engage publicly, ban quietly |
283
284### De-escalation Techniques
285
2861. **Acknowledge feelings** — "I can see this is frustrating"
2872. **Move to DM** — "Let's continue this privately"
2883. **Take a break** — "Let's pause and revisit tomorrow"
2894. **Clarify intent** — "I think there might be a misunderstanding"
2905. **Set boundaries** — "We're here to help, but not to be yelled at"
291
292### Moderator Self-Care
293
294| Risk | Mitigation |
295|------|------------|
296| Burnout | Rotate moderator duties |
297| Taking it personally | Remember: it's not about you |
298| Imposter syndrome | Regular team check-ins |
299| Isolation | Moderator private channel |
300
301---
302
303## Community-Led Growth
304
305### Word-of-Mouth Tactics
306
307| Tactic | How |
308|--------|-----|
309| **Referral program** | Rewards for invites that stick |
310| **Share-worthy content** | Exclusive insights, early access |
311| **Member spotlights** | Feature members → they share |
312| **Success stories** | "I got a job through this community" |
313
314### User-Generated Content
315
316| Content Type | How to Encourage |
317|--------------|------------------|
318| **Tutorials** | "Share your setup in #show-what-you-built" |
319| **Q&A threads** | Reward helpful answers |
320| **Project showcases** | Monthly demo events |
321| **Testimonials** | Ask happy members |
322
323### Community Champions
324
325Identify and empower super-users:
326
327| Champion Type | Role |
328|---------------|------|
329| **Greeters** | Welcome new members |
330| **Helpers** | Answer support questions |
331| **Content creators** | Tutorials, videos, guides |
332| **Event organizers** | Run community events |
333| **Connectors** | Introduce people to each other |
334
335---
336
337## Community Metrics
338
339### Health Dashboard
340
341| Metric | Healthy | Warning | Action Needed |
342|--------|---------|---------|---------------|
343| **Response time (support)** | <24h | 24-72h | >72h |
344| **Unanswered questions** | <10% | 10-25% | >25% |
345| **New member 7-day retention** | >40% | 20-40% | <20% |
346| **Monthly active ratio** | >20% | 10-20% | <10% |
347| **Moderator messages ratio** | <30% | 30-50% | >50% |
348
349### Growth Metrics
350
351| Metric | How to Track |
352|--------|-------------|
353| **Total members** | Platform analytics |
354| **Join rate** | New members per week |
355| **Churn rate** | Leaves per month |
356| **Engagement depth** | Messages per active user |
357| **Support success** | % questions resolved |
358
359---
360
361## Automation
362
363### Useful Bots (Discord)
364
365| Bot | Purpose |
366|-----|---------|
367| **MEE6 / Carl-bot** | Moderation, welcome messages, roles |
368| **Statbot** | Analytics and metrics |
369| **Ticket Tool** | Support ticket system |
370| **GitHub Bot** | Repo activity notifications |
371| **YAGPDB** | Advanced moderation, custom commands |
372
373### Automation Ideas
374
375| Automation | Benefit |
376|------------|---------|
377| Welcome DM | Consistent onboarding |
378| Auto-role on join | Immediate access |
379| Inactive member ping | Re-engagement |
380| Support ticket creation | Organized help |
381| GitHub notifications | Keep community informed |
382| Scheduled posts | Regular engagement |
383
384---
385
386## Tools
387
388| Tool | Use Case |
389|------|----------|
390| **[Octolens](https://octolens.com)** | Monitor community mentions across GitHub, Twitter, Reddit. Find where your community members talk about you. Track sentiment. Discover community content to amplify. |
391| **Commsor** | Community operations platform |
392| **Notion** | Community wiki and resources |
393| **Luma** | Event management |
394| **StreamYard/Restream** | Live event streaming |
395
396---
397
398## Related Skills
399
400- `developer-audience-context` — Know your community members
401- `open-source-marketing` — OSS community building
402- `developer-advocacy` — Personal brand in community
403- `developer-newsletter` — Community digest content
404
405## Limitations
406
407- Use this skill only when the task clearly matches its upstream source and local project context.
408- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
409- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.