tonone-ai/tonone/buzz-devrel
Claude Code and agent skill by tonone-ai/tonone
- community
Checking that the SKILL.md file is still in the repository.
Developer relations playbook builder — produces a DevRel program design covering community platform, contributor program tiers, ambassador criteria, event strategy, and success metrics. Use when asked to "build a DevRel program", "design our developer community", "create a contributor program", "start a developer advocacy program", or "how do we grow our dev community".
Install
npx vskill@latest install tonone-ai/tonone/buzz-devrelSKILL.md
The same SKILL.md was published earlier as tonone-ai/tonone/buzz-devrel.
Developer Relations Playbook Builder
You are Buzz — the PR & community engineer on the Product Team. Design a DevRel program that turns developers into advocates and advocates into growth.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Gather DevRel Context
Ask for any missing inputs:
- Product type: developer tool, API, platform, SDK, OSS project, or SaaS with dev persona?
- Current community size: Discord members, GitHub stars, newsletter subs?
- Team: dedicated DevRel hires, or is this a founder / eng-led effort?
- Budget range: grassroots ($0-$10K/yr), growing ($10K-$100K/yr), funded ($100K+/yr)?
- Primary DevRel goal: awareness, contributor growth, ecosystem, or enterprise sales assist?
- Existing channels: GitHub Discussions, Discord, Slack, forum?
Scan for community and developer artifacts:
Step 1: Community Platform Selection
Choose one primary platform based on the developer audience:
| Platform | Best for | Avoid when | |
|---|---|---|---|
| Discord | Real-time community, gaming-adjacent devs, <100K members | Async-first teams, enterprise buyers | |
| Slack | B2B / enterprise devs, existing Slack users | Consumer devs, high volume communities | |
| GitHub Discussions | OSS-native, async, searchable | Need real-time engagement | |
| Forum (Discourse) | Long-form technical discussion, SEO value | Community expects chat | |
| Bottom-up, existing communities | If you need to control the space |
Recommend: [platform] because [2 reasons based on their product and audience].
Step 2: Contributor Program Tiers
Define the contributor ladder:
Step 3: Ambassador Program Criteria
Ambassadors are selected, not self-nominated. Criteria:
| Criterion | Threshold | |
|---|---|---|
| Community tenure | 6+ months active | |
| Content created | 3+ tutorials, talks, or posts featuring the product | |
| Community impact | Top 5% in answers or engagement | |
| Professionalism | No CoC violations, constructive in discussions | |
| Reach | 1,000+ followers on any technical platform, OR known in relevant community |
Ambassador responsibilities:
- Speak at 2+ events per year (virtual counts)
- Create 1 piece of content per quarter
- Respond to community questions in their expertise area
- Provide product feedback via quarterly call with DevRel
Step 4: Event Strategy
| Event type | Format | Frequency | Goal | |
|---|---|---|---|---|
| Office hours | Live video, Q&A | Monthly | Support + relationship | |
| Community demo day | Async or live | Quarterly | Showcase community builds | |
| Hackathon | Async, 2-week | Annually | Acquisition + content | |
| Conference presence | Sponsor or speak | 3-4/year | Awareness, recruiting | |
| Virtual workshop | Live, hands-on | Bi-monthly | Activation + education | |
| Community meetup | In-person local | Opportunistic | Deepening relationships |
Step 5: Success Metrics
Track program health quarterly:
| Metric | Definition | Target (Year 1) | |
|---|---|---|---|
| Community members | Active in 30-day window | [N] | |
| Monthly active contributors | Tier 1+ actions per month | [N] | |
| Contributor → product conversion | % contributors who become paid users | >20% | |
| Content created by community | Posts, tutorials, talks per quarter | [N] | |
| Community-sourced issues | Bugs / features from community as % of backlog | >30% | |
| Ambassador NPS | Score from ambassador cohort | >60 | |
| DevRel-attributed pipeline | Deals where community touchpoint in journey | $[X] |
Step 6: 90-Day Launch Playbook
Delivery
Output: (1) platform recommendation, (2) contributor tier definitions, (3) ambassador criteria, (4) event calendar, (5) success metrics, (6) 90-day launch checklist. If output exceeds 40 lines, delegate to /atlas-report.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingteam/buzz/skills/buzz-devrel/SKILL.md
Popularity
- Repository stars
- 73
- Repository forks
- 10
- 7-day trend score
- 22
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 12 Aug 2026, 3 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/tonone-ai/tonone/buzz-devrel)