buzz-devrel
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".
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/buzz-devrel && cp -r /tmp/buzz-devrel/plugins/ai-agency/tonone/bundle/marketing-team/skills/buzz-devrel ~/.claude/skills/buzz-devrelSKILL.md
# 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: ```bash find . -name "*.md" 2>/dev/null | xargs grep -l "contributor\|community\|discord\|slack\|forum\|devrel\|developer.advocacy\|ambassador" 2>/dev/null | head -10 find . -name "CONTRIBUTING*" -o -name "CODE_OF_CONDUCT*" 2>/dev/null | head -5 ``` ### 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 | | Reddit | 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: ``` ## Contributor Program ### Tier 0 — User Entry: Create an account / install the SDK / use the API Benefit: Access to community, documentation, support channels Recognition: None required ### Tier 1 — Contributor Entry: File a bug report, open a PR, write a tutorial, answer 5 community questions Benefit: Contributor badge, mention in changelog, Discord role Recognition: Thank-you in release notes, monthly contributor highlight ### Tier 2 — Active Contributor Entry: 2+ merged PRs OR 20+ accepted community answers OR published community content Benefit: Early access to new features, 1:1 with DevRel team, swag Recognition: Featured in case study or blog post (with permission) ### Tier 3 — Ambassador Entry: Referral system (see Step 3), invited by DevRel team Benefit: Conference sponsorship, direct roadmap input, revenue share (if applicable) Recognition: Ambassador page on website, co-marketing opportunities ``` ### 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 i
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|