community-building – skill Lập trình cho agent AI
Khi người dùng muốn xây dựng, phát triển hoặc cải thiện cộng đồng lập trình viên trên Discord, Slack hoặc diễn đàn.
Cài skill community-building bằng một lệnh
Chọn công cụ bạn đang dùng, copy lệnh và dán vào terminal. Skill sẽ nằm trong thư mục skills của công cụ đó và sẵn sàng dùng ở phiên làm việc tiếp theo.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/community-building-9781f.tgz | tar xz -C ~/.claude/skills
Gọi trong Claude Code: /community-building – rồi mô tả công việc bạn muốn làm.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/community-building-9781f.tgz | tar xz -C ~/.codex/skills
Gọi trong Codex: $community-building – rồi mô tả công việc bạn muốn làm.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/community-building-9781f.tgz | tar xz -C ~/.hermes/skills
Gọi trong Hermes Agent: /community-building – rồi mô tả công việc bạn muốn làm.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/community-building-9781f.tgz | tar xz -C ~/.deepcode/skills
Gọi trong DeepSeek: /community-building – rồi mô tả công việc bạn muốn làm.
Nội dung SKILL.md
Nội dung SKILL.md gốc bằng tiếng Anh.
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 librariesSlack Channel Template
# welcome
# announcements (admin-only)
# general
# help
# random (off-topic)
# jobs (optional)
# introductions
# feedbackChannel 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 MemberWelcome 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 @moderatorsRole Assignment
| Role | How to Get | Permissions |
|------|------------|-------------|
| New Member | Auto on join | Limited channels |
| Member | Verify or time-based | Intended member channels only; no moderation/admin rights |
| 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.
Limit reports to authorized moderators on a need-to-know basis. Explain retention, investigation/escalation needs and platform access limits; do not promise absolute confidentiality.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
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
| 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 c
… (nội dung đầy đủ có trong gói tải về)
Skill liên quan
- redteam-mindset – Kỷ luật người vận hành red-team — các điều chỉnh tư duy giúp phân biệt kiểm thử tấn công…
- pyzotero – Quản lý thư viện tham khảo Zotero bằng client Python pyzotero: lấy, tạo, cập nhật và xóa…
- complexity-cuts – Giảm Big-O của mã hiện có theo quy trình từng biến đổi một, với kiểm chứng–hoàn…
- comprehensive-review-full-review – Dùng khi làm việc với comprehensive review full review.
- comprehensive-review-pr-enhance – Tạo mô tả PR có cấu trúc từ diff, thêm danh sách kiểm tra review, đánh giá rủi ro và tóm…
- concise-planning – Dùng khi người dùng yêu cầu kế hoạch cho một tác vụ lập trình, để tạo danh sách kiểm tra…
- conductor-revert – Hoàn tác có nhận biết Git theo đơn vị công việc logic (track, phase hoặc task)
- rust-async-patterns – Làm chủ lập trình bất đồng bộ trong Rust với Tokio, async trait, xử lý lỗi và các mẫu…