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