Building and growing developer communities from scratch to scale
Provides strategic guidance for launching and scaling developer communities on Discord, Slack, GitHub, or Discourse. Claude will use this when you need to create a community from scratch or diagnose engagement issues in existing communities.
/plugin marketplace add pluginagentmarketplace/custom-plugin-devrel-engineer/plugin install devrel-engineer-plugin@pluginagentmarketplace-devrel-engineerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/community-launch-plan.yamlreferences/COMMUNITY_GUIDE.mdscripts/community_health.pyCreate thriving developer communities that grow organically and deliver value.
parameters:
required:
- community_goal: string
- target_platform: enum[discord, slack, github, discourse]
optional:
- initial_size_target: integer
- budget: float
output:
launch_plan:
strategy: markdown
channel_structure: array[Channel]
success_metrics: object
Planning → Launch → Growth → Maturity → Scale
↓ ↓ ↓ ↓ ↓
Strategy Seed Engage Programs Leaders
Users Content Champions Autonomy
| Platform | Best For | Size | Key Feature |
|---|---|---|---|
| Discord | Real-time, casual | 100-50K | Roles, threads |
| Slack | Professional, B2B | 100-10K | Integrations |
| GitHub Discussions | OSS projects | Any | Code-linked |
| Discourse | Long-form | 1K-100K | SEO, archives |
1. Define community purpose and values
2. Choose platform and set up structure
3. Create welcome content and guidelines
4. Recruit 20-50 founding members
5. Seed initial conversations
1. Announce across channels
2. Host welcome event (AMA, office hours)
3. Personally welcome every new member
4. Start daily engagement cadence
5. Gather early feedback
| Stage | Tactic | Goal |
|---|---|---|
| 0-100 | Personal invitations | Quality seed |
| 100-500 | Content marketing | Organic growth |
| 500-2K | Events, partnerships | Momentum |
| 2K-10K | Champion program | Scale |
| 10K+ | Self-sustaining | Autonomy |
retry_patterns:
low_engagement:
strategy: "Personal outreach to top 20 members"
escalation: "AMA or exclusive event"
member_churn:
strategy: "Exit survey, re-engagement campaign"
toxic_behavior:
strategy: "Private warning, then public reminder"
| Failure Mode | Detection | Recovery |
|---|---|---|
| Ghost town | <5 messages/day | Seed content, personal pings |
| Toxic culture | Complaints | Enforce CoC, public statement |
| Off-topic drift | Unrelated posts | Redirect, add channels |
□ Community purpose clearly stated?
□ Platform analytics configured?
□ Code of conduct visible?
□ Welcome message set up?
□ Initial content seeded?
□ Moderator coverage scheduled?
□ Recognition system active?
test_community_building:
unit_tests:
- test_onboarding_flow:
assert: "Welcome message within 1 min"
integration_tests:
- test_member_journey:
assert: "First post → Reply within 24h"
| Metric | Target |
|---|---|
| Monthly Active Users | 30%+ of total |
| Messages per member | 5+ per month |
| Response time | <4 hours |
| Member retention | 80%+ at 30 days |
metrics:
- total_members: integer
- mau: integer
- messages_per_day: integer
- response_time_avg: duration
See assets/ for community templates.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.