[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F4TYRCMD5M4SQTCE7X4HDY":3,"skill-same:01M6F4TYRCMD5M4SQTCE7X4HDY":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":30,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M6F4TYRCMD5M4SQTCE7X4HDY","community-building",null,"When the user wants to build, grow, or improve a developer community on Discord, Slack, or forums.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-community-building\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"community building","community","main","2026","when","blob","tree","forums","critical","grow","wed","discord","build","user","improve","developer","https","license","github","slack","2026-11-10 10:12:30",false,"---\nname: community-building\ndescription: \"When the user wants to build, grow, or improve a developer community on Discord, Slack, or forums.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fcommunity-building\nsource_repo: jonathimer\u002Fdevmarketing-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Community Building\n## When to Use\n\nUse 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...\n\n\nThis 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.\n\n---\n\n## Before You Start\n\n**Load your audience context first.** Read `.agents\u002Fdeveloper-audience-context.md` to understand:\n\n- Who your developers are (role, seniority, interests)\n- Where they already hang out (to avoid competing platforms)\n- What problems they discuss (community topic focus)\n- How they communicate (formal vs. casual tone)\n\nIf the context file doesn't exist, run the `developer-audience-context` skill first.\n\n---\n\n## Platform Selection\n\n### Comparison Matrix\n\n| Platform | Best For | Pros | Cons |\n|----------|----------|------|------|\n| **Discord** | Developer tools, gaming, OSS | Real-time, rich features, free | Can be chaotic, less enterprise |\n| **Slack** | Enterprise, B2B SaaS | Professional, familiar | Expensive at scale, message limits |\n| **GitHub Discussions** | OSS projects | Integrated, async, searchable | Less community feel |\n| **Discourse** | Long-form, searchable | SEO, threading, ownership | Maintenance, hosting costs |\n| **Circle** | Courses, paid communities | Courses integration, clean | Paid, less developer-native |\n\n### Decision Framework\n\n| If your audience is... | Consider |\n|------------------------|----------|\n| Individual developers, OSS | Discord |\n| Enterprise teams | Slack |\n| Technical, async-preferred | GitHub Discussions |\n| Mixed, need searchability | Discourse |\n| Course\u002Feducation based | Circle |\n\n---\n\n## Channel Structure\n\n### Discord Channel Template\n\n```\n? INFORMATION\n├── #welcome — First landing, rules, links\n├── #announcements — Official updates (admin-only posting)\n├── #rules — Code of conduct\n└── #introductions — New member intros\n\n? GENERAL\n├── #general — Main discussion\n├── #off-topic — Non-project chat\n└── #show-what-you-built — Share projects\n\n❓ SUPPORT\n├── #help — General questions\n├── #troubleshooting — Bug help\n└── #feature-requests — Suggestions\n\n? TECHNICAL\n├── #backend — Backend discussions\n├── #frontend — Frontend discussions\n└── #devops — Infrastructure discussions\n\n? COMMUNITY\n├── #jobs — Job postings (if allowed)\n├── #events — Meetups, conferences\n└── #content — Blog posts, videos\n\n? RESOURCES\n├── #learning — Tutorials, courses\n└── #tools — Useful tools and libraries\n```\n\n### Slack Channel Template\n\n```\n# welcome\n# announcements (admin-only)\n# general\n# help\n# random (off-topic)\n# jobs (optional)\n# introductions\n# feedback\n```\n\n### Channel Guidelines\n\n| Channel Type | Posting Rules | Moderation Level |\n|--------------|---------------|------------------|\n| **Announcements** | Admin only | N\u002FA |\n| **General** | On-topic discussion | Light |\n| **Help** | Questions welcome, be patient | Medium |\n| **Off-topic** | Anything goes (within CoC) | Light |\n| **Jobs** | Structured format required | Heavy |\n| **Introductions** | One post per person | Light |\n\n---\n\n## Onboarding Experience\n\n### New Member Journey\n\n```\nJoin Server\n    ↓\nWelcome Message (DM or public)\n    ↓\nRead Rules \u002F Accept\n    ↓\nVerify (optional: GitHub, email)\n    ↓\nIntroduce Yourself\n    ↓\nFirst Interaction\n    ↓\nRegular Member\n```\n\n### Welcome Message Template\n\n**Discord DM:**\n```\nWelcome to [Community Name]! ?\n\nHere's how to get started:\n\n1. Read the rules in #rules\n2. Introduce yourself in #introductions\n3. Ask questions in #help — we're friendly!\n\nQuick links:\n• Documentation: [link]\n• Getting started: [link]\n• GitHub: [link]\n\nWe're glad you're here!\n```\n\n**Public #welcome channel:**\n```\n# Welcome to [Community Name]!\n\nWe're [brief description of who you are and what you do].\n\n## Quick Start\n\n1. **Read the rules** → #rules\n2. **Introduce yourself** → #introductions\n3. **Get help** → #help\n4. **Chat with us** → #general\n\n## Useful Links\n\n- [Documentation]\n- [GitHub]\n- [Website]\n\n## Questions?\n\nDrop a message in #help or mention @moderators\n```\n\n### Role Assignment\n\n| Role | How to Get | Permissions |\n|------|------------|-------------|\n| **New Member** | Auto on join | Limited channels |\n| **Member** | Verify or time-based | Intended member channels only; no moderation\u002Fadmin rights |\n| **Contributor** | PR merged, active helper | Badge, special channel |\n| **Moderator** | Invited | Moderation powers |\n| **Admin** | Core team | Full access |\n\n---\n\n## Engagement Programs\n\n### Discussion Prompts\n\nSchedule regular engagement:\n\n| Day | Prompt Type | Example |\n|-----|-------------|---------|\n| Monday | This week's goals | \"What are you working on this week?\" |\n| Wednesday | Technical question | \"Controversial: Tabs or spaces?\" |\n| Friday | Show & Tell | \"Share what you shipped this week\" |\n\n### Recognition Programs\n\n| Program | Description | Frequency |\n|---------|-------------|-----------|\n| **Contributor of the Month** | Recognize top helpers | Monthly |\n| **First PR Celebration** | Welcome new contributors | As happens |\n| **Milestone Badges** | 10\u002F50\u002F100 messages | Automatic |\n| **Expert Roles** | Domain expertise recognition | Quarterly |\n\n### Event Ideas\n\n| Event Type | Format | Effort |\n|------------|--------|--------|\n| **Office Hours** | Live Q&A with team | Low |\n| **Show & Tell** | Members demo projects | Low |\n| **Workshops** | Teaching sessions | Medium |\n| **Hackathons** | Build challenges | High |\n| **Game Night** | Non-tech fun | Low |\n| **AMA Sessions** | Guest experts | Medium |\n\n### Engagement Metrics\n\n| Metric | What It Tells You |\n|--------|------------------|\n| **DAU\u002FMAU** | Daily vs monthly active users |\n| **Messages per user** | Individual engagement depth |\n| **Questions answered** | Community self-sufficiency |\n| **New member retention** | Onboarding effectiveness |\n| **Event attendance** | Program resonance |\n\n---\n\n## Handling Toxicity\n\n### Code of Conduct Essentials\n\n```markdown\n# Code of Conduct\n\n## Our Standards\n\n**Do:**\n- Be respectful and inclusive\n- Help others learn (no \"RTFM\")\n- Assume good intentions\n- Give constructive feedback\n- Report problems, don't engage\n\n**Don't:**\n- Personal attacks or harassment\n- Discrimination of any kind\n- Spam or self-promotion\n- NSFW content\n- Doxxing or privacy violations\n- Bad faith arguments\n\n## Enforcement\n\n1. **Warning** — First offense, good faith\n2. **Temp mute** — Repeated issues\n3. **Temp ban** — Serious violations\n4. **Permanent ban** — Egregious or repeated\n\n## Reporting\n\nDM any @moderator or use the report feature.\nLimit reports to authorized moderators on a need-to-know basis. Explain retention, investigation\u002Fescalation needs and platform access limits; do not promise absolute confidentiality.\n```\n\n### Moderation Playbook\n\n| Situation | Response |\n|-----------|----------|\n| **Heated debate** | \"Let's keep this constructive. Both perspectives have merit.\" |\n| **Help vampire** | \"Here's a guide on asking good questions: [link]\" |\n| **Self-promotion spam** | Delete, warn, or ban depending on frequency |\n| **Off-topic drift** | \"Great discussion! Let's move this to #off-topic\" |\n| **Harassment** | Immediate mute, investigate, likely ban |\n| **Bad faith troll** | Don't engage publicly, ban quietly |\n\n### De-escalation Techniques\n\n1. **Acknowledge feelings** — \"I can see this is frustrating\"\n2. **Move to DM** — \"Let's continue this privately\"\n3. **Take a break** — \"Let's pause and revisit tomorrow\"\n4. **Clarify intent** — \"I think there might be a misunderstanding\"\n5. **Set boundaries** — \"We're here to help, but not to be yelled at\"\n\n### Moderator Self-Care\n\n| Risk | Mitigation |\n|------|------------|\n| Burnout | Rotate moderator duties |\n| Taking it personally | Remember: it's not about you |\n| Imposter syndrome | Regular team check-ins |\n| Isolation | Moderator private channel |\n\n---\n\n## Community-Led Growth\n\n### Word-of-Mouth Tactics\n\n| Tactic | How |\n|--------|-----|\n| **Referral program** | Rewards for invites that stick |\n| **Share-worthy content** | Exclusive insights, early access |\n| **Member spotlights** | Feature members → they share |\n| **Success stories** | \"I got a job through this community\" |\n\n### User-Generated Content\n\n| Content Type | How to Encourage |\n|--------------|------------------|\n| **Tutorials** | \"Share your setup in #show-what-you-built\" |\n| **Q&A threads** | Reward helpful answers |\n| **Project showcases** | Monthly demo events |\n| **Testimonials** | Ask happy members |\n\n### Community Champions\n\nIdentify and empower super-users:\n\n| Champion Type | Role |\n|---------------|------|\n| **Greeters** | Welcome new members |\n| **Helpers** | Answer support questions |\n| **Content creators** | Tutorials, videos, guides |\n| **Event organizers** | Run community events |\n| **Connectors** | Introduce people to each other |\n\n---\n\n## Community Metrics\n\n### Health Dashboard\n\n| Metric | Healthy | Warning | Action Needed |\n|--------|---------|---------|---------------|\n| **Response time (support)** | \u003C24h | 24-72h | >72h |\n| **Unanswered questions** | \u003C10% | 10-25% | >25% |\n| **New member 7-day retention** | >40% | 20-40% | \u003C20% |\n| **Monthly active ratio** | >20% | 10-20% | \u003C10% |\n| **Moderator messages ratio** | \u003C30% | 30-50% | >50% |\n\n### Growth Metrics\n\n| Metric | How to Track |\n|--------|-------------|\n| **Total members** | Platform analytics |\n| **Join rate** | New members per week |\n| **Churn rate** | Leaves per month |\n| **Engagement depth** | Messages per active user |\n| **Support success** | % questions resolved |\n\n---\n\nThe health thresholds above are illustrative targets, not validated industry benchmarks. Define active\u002Fretained, observation windows, timezone\u002Fsupport coverage and cohort denominators before comparing them. Moderation severity may justify skipping warning stages; document evidence, conflict-of-interest handling and an appeal route.\n\n## Automation\n\n### Useful Bots (Discord)\n\n| Bot | Purpose |\n|-----|---------|\n| **MEE6 \u002F Carl-bot** | Moderation, welcome messages, roles |\n| **Statbot** | Analytics and metrics |\n| **Ticket Tool** | Support ticket system |\n| **GitHub Bot** | Repo activity notifications |\n| **YAGPDB** | Advanced moderation, custom commands |\n\nInstalling bots, granting permissions, scheduling posts, sending DMs\u002Fpings and changing member access require authorization for the server, recipient and operation. Minimize bot scopes\u002Fdata collection and support opt-outs; drafting a community plan does not send anything.\n\n### Automation Ideas\n\n| Automation | Benefit |\n|------------|---------|\n| Welcome DM | Consistent onboarding |\n| Auto-role on join | Immediate access |\n| Inactive member ping | Re-engagement |\n| Support ticket creation | Organized help |\n| GitHub notifications | Keep community informed |\n| Scheduled posts | Regular engagement |\n\n---\n\n## Tools\n\n| Tool | Use Case |\n|------|----------|\n| **[Octolens](https:\u002F\u002Foctolens.com)** | Monitor community mentions across GitHub, Twitter, Reddit. Find where your community members talk about you. Track sentiment. Discover community content to amplify. |\n| **Commsor** | Community operations platform |\n| **Notion** | Community wiki and resources |\n| **Luma** | Event management |\n| **StreamYard\u002FRestream** | Live event streaming |\n\n---\n\n## Related Skills\n\n- `developer-audience-context` — Know your community members\n- `open-source-marketing` — OSS community building\n- `developer-advocacy` — Personal brand in community\n- `developer-newsletter` — Community digest content\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Community Building\n## When to Use\n\nUse 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...\n\n\nThis 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.\n\n---\n\n## Before You Start\n\n**Load your audience context first.** Read `.agents\u002Fdeveloper-audience-context.md` to understand:\n\n- Who your developers are (role, seniority, interests)\n- Where they already hang out (to avoid competing platforms)\n- What problems they discuss (community topic focus)\n- How they communicate (formal vs. casual tone)\n\nIf the context file doesn't exist, run the `developer-audience-context` skill first.\n\n---\n\n## Platform Selection\n\n### Comparison Matrix\n\n| Platform | Best For | Pros | Cons |\n|----------|----------|------|------|\n| **Discord** | Developer tools, gaming, OSS | Real-time, rich features, free | Can be chaotic, less enterprise |\n| **Slack** | Enterprise, B2B SaaS | Professional, familiar | Expensive at scale, message limits |\n| **GitHub Discussions** | OSS projects | Integrated, async, searchable | Less community feel |\n| **Discourse** | Long-form, searchable | SEO, threading, ownership | Maintenance, hosting costs |\n| **Circle** | Courses, paid communities | Courses integration, clean | Paid, less developer-native |\n\n### Decision Framework\n\n| If your audience is... | Consider |\n|------------------------|----------|\n| Individual developers, OSS | Discord |\n| Enterprise teams | Slack |\n| Technical, async-preferred | GitHub Discussions |\n| Mixed, need searchability | Discourse |\n| Course\u002Feducation based | Circle |\n\n---\n\n## Channel Structure\n\n### Discord Channel Template\n\n```\n? INFORMATION\n├── #welcome — First landing, rules, links\n├── #announcements — Official updates (admin-only posting)\n├── #rules — Code of conduct\n└── #introductions — New member intros\n\n? GENERAL\n├── #general — Main discussion\n├── #off-topic — Non-project chat\n└── #show-what-you-built — Share projects\n\n❓ SUPPORT\n├── #help — General questions\n├── #troubleshooting — Bug help\n└── #feature-requests — Suggestions\n\n? TECHNICAL\n├── #backend — Backend discussions\n├── #frontend — Frontend discussions\n└── #devops — Infrastructure discussions\n\n? COMMUNITY\n├── #jobs — Job postings (if allowed)\n├── #events — Meetups, conferences\n└── #content — Blog posts, videos\n\n? RESOURCES\n├── #learning — Tutorials, courses\n└── #tools — Useful tools and libraries\n```\n\n### Slack Channel Template\n\n```\n# welcome\n# announcements (admin-only)\n# general\n# help\n# random (off-topic)\n# jobs (optional)\n# introductions\n# feedback\n```\n\n### Channel Guidelines\n\n| Channel Type | Posting Rules | Moderation Level |\n|--------------|---------------|------------------|\n| **Announcements** | Admin only | N\u002FA |\n| **General** | On-topic discussion | Light |\n| **Help** | Questions welcome, be patient | Medium |\n| **Off-topic** | Anything goes (within CoC) | Light |\n| **Jobs** | Structured format required | Heavy |\n| **Introductions** | One post per person | Light |\n\n---\n\n## Onboarding Experience\n\n### New Member Journey\n\n```\nJoin Server\n    ↓\nWelcome Message (DM or public)\n    ↓\nRead Rules \u002F Accept\n    ↓\nVerify (optional: GitHub, email)\n    ↓\nIntroduce Yourself\n    ↓\nFirst Interaction\n    ↓\nRegular Member\n```\n\n### Welcome Message Template\n\n**Discord DM:**\n```\nWelcome to [Community Name]! ?\n\nHere's how to get started:\n\n1. Read the rules in #rules\n2. Introduce yourself in #introductions\n3. Ask questions in #help — we're friendly!\n\nQuick links:\n• Documentation: [link]\n• Getting started: [link]\n• GitHub: [link]\n\nWe're glad you're here!\n```\n\n**Public #welcome channel:**\n```\n# Welcome to [Community Name]!\n\nWe're [brief description of who you are and what you do].\n\n## Quick Start\n\n1. **Read the rules** → #rules\n2. **Introduce yourself** → #introductions\n3. **Get help** → #help\n4. **Chat with us** → #general\n\n## Useful Links\n\n- [Documentation]\n- [GitHub]\n- [Website]\n\n## Questions?\n\nDrop a message in #help or mention @moderators\n```\n\n### Role Assignment\n\n| Role | How to Get | Permissions |\n|------|------------|-------------|\n| **New Member** | Auto on join | Limited channels |\n| **Member** | Verify or time-based | Intended member channels only; no moderation\u002Fadmin rights |\n| **Contributor** | PR merged, active helper | Badge, special channel |\n| **Moderator** | Invited | Moderation powers |\n| **Admin** | Core team | Full access |\n\n---\n\n## Engagement Programs\n\n### Discussion Prompts\n\nSchedule regular engagement:\n\n| Day | Prompt Type | Example |\n|-----|-------------|---------|\n| Monday | This week's goals | \"What are you working on this week?\" |\n| Wednesday | Technical question | \"Controversial: Tabs or spaces?\" |\n| Friday | Show & Tell | \"Share what you shipped this week\" |\n\n### Recognition Programs\n\n| Program | Description | Frequency |\n|---------|-------------|-----------|\n| **Contributor of the Month** | Recognize top helpers | Monthly |\n| **First PR Celebration** | Welcome new contributors | As happens |\n| **Milestone Badges** | 10\u002F50\u002F100 messages | Automatic |\n| **Expert Roles** | Domain expertise recognition | Quarterly |\n\n### Event Ideas\n\n| Event Type | Format | Effort |\n|------------|--------|--------|\n| **Office Hours** | Live Q&A with team | Low |\n| **Show & Tell** | Members demo projects | Low |\n| **Workshops** | Teaching sessions | Medium |\n| **Hackathons** | Build challenges | High |\n| **Game Night** | Non-tech fun | Low |\n| **AMA Sessions** | Guest experts | Medium |\n\n### Engagement Metrics\n\n| Metric | What It Tells You |\n|--------|------------------|\n| **DAU\u002FMAU** | Daily vs monthly active users |\n| **Messages per user** | Individual engagement depth |\n| **Questions answered** | Community self-sufficiency |\n| **New member retention** | Onboarding effectiveness |\n| **Event attendance** | Program resonance |\n\n---\n\n## Handling Toxicity\n\n### Code of Conduct Essentials\n\n```markdown\n# Code of Conduct\n\n## Our Standards\n\n**Do:**\n- Be respectful and inclusive\n- Help others learn (no \"RTFM\")\n- Assume good intentions\n- Give constructive feedback\n- Report problems, don't engage\n\n**Don't:**\n- Personal attacks or harassment\n- Discrimination of any kind\n- Spam or self-promotion\n- NSFW content\n- Doxxing or privacy violations\n- Bad faith arguments\n\n## Enforcement\n\n1. **Warning** — First offense, good faith\n2. **Temp mute** — Repeated issues\n3. **Temp ban** — Serious violations\n4. **Permanent ban** — Egregious or repeated\n\n## Reporting\n\nDM any @moderator or use the report feature.\nLimit reports to authorized moderators on a need-to-know basis. Explain retention, investigation\u002Fescalation needs and platform access limits; do not promise absolute confidentiality.\n```\n\n### Moderation Playbook\n\n| Situation | Response |\n|-----------|----------|\n| **Heated debate** | \"Let's keep this constructive. Both perspectives have merit.\" |\n| **Help vampire** | \"Here's a guide on asking good questions: [link]\" |\n| **Self-promotion spam** | Delete, warn, or ban depending on frequency |\n| **Off-topic drift** | \"Great discussion! Let's move this to #off-topic\" |\n| **Harassment** | Immediate mute, investigate, likely ban |\n| **Bad faith troll** | Don't engage publicly, ban quietly |\n\n### De-escalation Techniques\n\n1. **Acknowledge feelings** — \"I can see this is frustrating\"\n2. **Move to DM** — \"Let's continue this privately\"\n3. **Take a break** — \"Let's pause and revisit tomorrow\"\n4. **Clarify intent** — \"I think there might be a misunderstanding\"\n5. **Set boundaries** — \"We're here to help, but not to be yelled at\"\n\n### Moderator Self-Care\n\n| Risk | Mitigation |\n|------|------------|\n| Burnout | Rotate moderator duties |\n| Taking it personally | Remember: it's not about you |\n| Imposter syndrome | Regular team check-ins |\n| Isolation | Moderator private channel |\n\n---\n\n## Community-Led Growth\n\n### Word-of-Mouth Tactics\n\n| Tactic | How |\n|--------|-----|\n| **Referral program** | Rewards for invites that stick |\n| **Share-worthy content** | Exclusive insights, early access |\n| **Member spotlights** | Feature members → they share |\n| **Success stories** | \"I got a job through this community\" |\n\n### User-Generated Content\n\n| Content Type | How to Encourage |\n|--------------|------------------|\n| **Tutorials** | \"Share your setup in #show-what-you-built\" |\n| **Q&A threads** | Reward helpful answers |\n| **Project showcases** | Monthly demo events |\n| **Testimonials** | Ask happy members |\n\n### Community Champions\n\nIdentify and empower super-users:\n\n| Champion Type | Role |\n|---------------|------|\n| **Greeters** | Welcome new members |\n| **Helpers** | Answer support questions |\n| **Content creators** | Tutorials, videos, guides |\n| **Event organizers** | Run community events |\n| **Connectors** | Introduce people to each other |\n\n---\n\n## Community Metrics\n\n### Health Dashboard\n\n| Metric | Healthy | Warning | Action Needed |\n|--------|---------|---------|---------------|\n| **Response time (support)** | \u003C24h | 24-72h | >72h |\n| **Unanswered questions** | \u003C10% | 10-25% | >25% |\n| **New member 7-day retention** | >40% | 20-40% | \u003C20% |\n| **Monthly active ratio** | >20% | 10-20% | \u003C10% |\n| **Moderator messages ratio** | \u003C30% | 30-50% | >50% |\n\n### Growth Metrics\n\n| Metric | How to Track |\n|--------|-------------|\n| **Total members** | Platform analytics |\n| **Join rate** | New members per week |\n| **Churn rate** | Leaves per month |\n| **Engagement depth** | Messages per active user |\n| **Support success** | % questions resolved |\n\n---\n\nThe health thresholds above are illustrative targets, not validated industry benchmarks. Define active\u002Fretained, observation windows, timezone\u002Fsupport coverage and cohort denominators before comparing them. Moderation severity may justify skipping warning stages; document evidence, conflict-of-interest handling and an appeal route.\n\n## Automation\n\n### Useful Bots (Discord)\n\n| Bot | Purpose |\n|-----|---------|\n| **MEE6 \u002F Carl-bot** | Moderation, welcome messages, roles |\n| **Statbot** | Analytics and metrics |\n| **Ticket Tool** | Support ticket system |\n| **GitHub Bot** | Repo activity notifications |\n| **YAGPDB** | Advanced moderation, custom commands |\n\nInstalling bots, granting permissions, scheduling posts, sending DMs\u002Fpings and changing member access require authorization for the server, recipient and operation. Minimize bot scopes\u002Fdata collection and support opt-outs; drafting a community plan does not send anything.\n\n### Automation Ideas\n\n| Automation | Benefit |\n|------------|---------|\n| Welcome DM | Consistent onboarding |\n| Auto-role on join | Immediate access |\n| Inactive member ping | Re-engagement |\n| Support ticket creation | Organized help |\n| GitHub notifications | Keep community informed |\n| Scheduled posts | Regular engagement |\n\n---\n\n## Tools\n\n| Tool | Use Case |\n|------|----------|\n| **[Octolens](https:\u002F\u002Foctolens.com)** | Monitor community mentions across GitHub, Twitter, Reddit. Find where your community members talk about you. Track sentiment. Discover community content to amplify. |\n| **Commsor** | Community operations platform |\n| **Notion** | Community wiki and resources |\n| **Luma** | Event management |\n| **StreamYard\u002FRestream** | Live event streaming |\n\n---\n\n## Related Skills\n\n- `developer-audience-context` — Know your community members\n- `open-source-marketing` — OSS community building\n- `developer-advocacy` — Personal brand in community\n- `developer-newsletter` — Community digest content\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":36,"source":53,"license":14,"date_added":54,"description":7,"source_repo":55,"source_type":29,"license_source":56},"https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fcommunity-building",1782864000000,"jonathimer\u002Fdevmarketing-skills","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-community-building",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-12 14:21:24",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add boisenoise\u002Fskills-collections --skill community-building",{"tool":69,"command":70},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill community-building",{"tool":72,"command":73},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill community-building","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-community-building\u002FSKILL.md",true,[77],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"README.md","REFERENCE","参考文档",2634,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-community-building\u002FREADME.md",[84,111,134,157,176,199],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":48},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,36,108,109,110,32,31],"web","access","web access","official","development","browser","search","data","Tools","read","fetch","only","youtube","free tools","platform","free","cover","normal",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":48},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[113,122,123,46,96,97,45,101,124,125,126,127,128,129,130,36,131,132,133,33,31],"MCP","cli","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":48},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源",[136,46,96,45,44,145,146,147,148,149,36,150,151,152,132,153,154,155,156,33,113,31],"email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":48},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[165,166,167,46,96,45,168,169,44,170,124,171,172,173,148,36,174,175,33,113,31],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":48},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[184,185,46,186,96,187,45,188,189,190,191,192,36,193,194,195,196,197,198,33],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":48},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[207,208,209,46,96,45,210,211,147,212,213,36,214,215,216,217,218,219,220,33],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]