// Load when working on developer community engagement, technical advocacy, developer experience content, or community building. Contains best practices for Developer Relations (DevRel) and community management.
[HINT] 下载包含 SKILL.md 和所有相关文件的完整技能目录
| name | devrel-practices |
| description | Load when working on developer community engagement, technical advocacy, developer experience content, or community building. Contains best practices for Developer Relations (DevRel) and community management. |
Developer Relations builds authentic connections between developers and technology. The goal is mutual value creation:
Technical credibility is essential. DevRel must:
Create valuable technical content:
Build and nurture developer communities:
Innovate in engagement approaches:
Developers join communities for:
Sustainable Engagement Focus on depth over constant presence:
## Weekly Rhythm
- Monday: Share learning resource
- Wednesday: Answer community questions
- Friday: Highlight community member work
## Monthly Events
- Week 1: Office hours / AMA
- Week 2: Workshop or tutorial
- Week 3: Community showcase
- Week 4: Planning/feedback session
Scaling Community Management
## Tier 1: Self-Service (80%)
- Comprehensive documentation
- FAQs and knowledge base
- Community-answered questions
- Searchable archives
## Tier 2: Community-Powered (15%)
- Peer-to-peer support
- Ambassador responses
- Community moderators
- User-generated content
## Tier 3: Direct Engagement (5%)
- Complex technical issues
- Strategic relationships
- High-value contributors
- Escalated concerns
Channel Structure
📢 announcements (read-only)
👋 introductions
💬 general
❓ help
├── python-help
├── data-viz-help
└── ml-help
📚 resources
🎉 showcase
💡 ideas
🤝 jobs-networking (optional)
Moderation Guidelines
Know Your Audience
## Audience Segments
- Beginners: Need fundamentals, no assumptions
- Intermediate: Want best practices, patterns
- Advanced: Seek optimization, edge cases
- Decision Makers: Care about business value
Developer-First Content Principles
Structure Template
# [Problem-Focused Title]
## TL;DR
[3-sentence summary with code snippet]
## The Problem
[Relatable scenario developers face]
## The Solution
[Clear explanation with code]
## Step-by-Step Implementation
[Detailed walkthrough]
## Going Further
[Advanced tips, alternatives, resources]
## Conclusion
[Key takeaways and call to action]
Stream Format
## Pre-Stream (10 min before)
- Test audio/video
- Set up code environment
- Have reference docs open
## Stream Structure
1. Hook (0-2 min): What we're building
2. Context (2-5 min): Why this matters
3. Setup (5-10 min): Prerequisites
4. Build (20-40 min): Main content
5. Q&A (5-10 min): Audience questions
6. Close (2 min): Summary and next steps
## Tiers
1. **Contributors**: Occasional participation
- Share content
- Report bugs
- Provide feedback
2. **Ambassadors**: Regular engagement
- Create content
- Speak at events
- Mentor newcomers
3. **Champions**: Deep involvement
- Lead initiatives
- Strategic input
- Public representation
## What Ambassadors Give
- Content creation
- Event speaking
- Community support
- Product feedback
## What Ambassadors Receive
- Early access / beta features
- Recognition and visibility
- Professional development
- Networking opportunities
- (Optional) Swag, compensation
## Awareness
- Content views/reads
- Social reach
- SEO rankings
- Newsletter subscribers
## Engagement
- GitHub stars, forks
- Discord active members
- Event attendance
- Content completion rates
## Adoption
- New users/signups
- Tutorial completions
- API calls
- Project implementations
# DevRel Monthly Report - [Month Year]
## Highlights
- [Top achievement 1]
- [Top achievement 2]
- [Top achievement 3]
## Content
| Type | Published | Views | Engagement |
|------|-----------|-------|------------|
| Blog posts | X | X | X% |
| Tutorials | X | X | X% |
| Videos | X | X | X% |
## Community
- Active members: X (+X% MoM)
- Questions answered: X
- Events held: X
## Looking Ahead
- [Next month priority 1]
- [Next month priority 2]