开发者关系项目规划指南
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "buzz-devrel":https://skillpi.com/zh/skills/deepskill-bb850ded03c63a7c50fabd067bd903c43f2ce78b64eb1b7328143f3108eb2ad9。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/marketing-team/skills/buzz-devrel/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/marketing-team/skills/buzz-devrel --skill buzz-devrel来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
根据产品、社区、团队和目标,规划社区平台、贡献者层级、大使标准、活动策略及成功指标,并形成启动清单。适合设计 DevRel 项目的团队;生成的方案需结合真实预算、社区现状和可用人力复核。
文件浏览
--- name: buzz-devrel description: 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". allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion version: 0.1.0 author: tonone-ai <hello@tonone.ai> license: MIT --- # 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 in journey | $[X] | ### Step 6: 90-Day Launch Playbook ``` Month 1 — Foundation [ ] Choose and configure community platform [ ] Write and publish Code of Conduct [ ] Write and publish Contribution Guide [ ] Identify and personally invite first 20 seed members [ ] Set up onboarding flow for new members (welcome message, where to start) Month 2 — First Programs [ ] Host first office hours [ ] Launch Tier 1 contributor recognition (retroactive for existing contributors) [ ] Publish first community highlight / newsletter [ ] Identify ambassador candidates (Tier 3 criteria) Month 3 — Momentum [ ] Announce ambassador program [ ] Launch first community challenge or mini-hackathon [ ] Publish quarterly metrics (transparency builds trust) [ ] First external DevRel content (talk, podcast, blog post) ``` ## 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.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供完整的开发者关系项目设计方案,涵盖社区平台、贡献者计划、大使标准、活动策略和成功指标
评分依据
触发词精准完整,覆盖多种变体,边界清晰
评分依据
Phase/步骤清晰,有出口条件,含端到端示例,frontmatter完整,单文件≤500行
评分依据
工具来源明确,参数正确,覆盖主要异常,不可逆操作有确认机制
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。