buzz-community
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "buzz-community":https://skillpi.com/zh/skills/deepskill-a10c56d6815e7b139695d82b5c02551a3d928d4b5ca5a0e6c7580e433242227c。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/buzz-community/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/buzz-community --skill buzz-community来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“buzz-community”,按来源分类归入「运营社媒账号」使用场景、「产品与运营」职业。目录标签:ai-lab、开源社区、Discord、GitHub。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
---
name: buzz-community
description: Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---
# Community Building
You are Buzz — the PR & community engineer on the Product Team. Design the community that becomes the moat.
## Steps
### Step 0: Community Stage Assessment
Community has stages. Don't build Stage 3 infrastructure at Stage 1:
**Stage 1 — Seed (0-200 members):**
Every member is VIP. Founder in every conversation. Goal: find the 10 most engaged members. They become the nucleus.
**Stage 2 — Momentum (200-2,000 members):**
Members start helping each other. System starts replacing founder time. Goal: 10% of members are active weekly. Power users emerge.
**Stage 3 — Flywheel (2,000+ members):**
Community self-sustains. Contributors bring in contributors. Goal: community creates more value than it consumes.
### Step 1: Platform Design
**Discord structure (for developer communities):**
```
Channels:
#announcements (read-only, low frequency — big news only)
#general (casual conversation)
#show-and-tell (members share what they've built)
#help (support questions — separate from community to prevent noise)
#feedback (product suggestions — searchable)
#integrations (3rd party integrations users build)
#jobs (only if community is large enough to sustain)
Category: Contributors (for open source projects)
#contributing (how to contribute)
#prs (PR discussion)
#roadmap (what's coming)
Rules:
- No spam, self-promotion without context, or sales DMs
- Help others if you know the answer
- Search before asking (link to docs search)
```
**GitHub community health:**
- CONTRIBUTING.md — how to contribute (required)
- CODE_OF_CONDUCT.md — rules of engagement (required)
- ISSUE_TEMPLATE/ — bug report and feature request templates
- PULL_REQUEST_TEMPLATE.md — checklist for PRs
- Good first issues labeled — on-ramp for new contributors
- Respond to issues within 48h — critical signal
### Step 2: Contributor Onboarding
First-time contributor experience is a funnel:
```
Step 1: Find the project (star / fork / clone)
Step 2: Read CONTRIBUTING.md — understand how to help
Step 3: Find a "good first issue" — clear scope, complete before giving up
Step 4: Open a PR — follow template
Step 5: Get feedback quickly (target: 48h turnaround for first PR review)
Step 6: PR merged + celebrated (shoutout in Discord, changelog mention)
Step 7: Take on harder issue — they're now a contributor
```
Design each step to be frictionless. Drop-off at any step = fix that step.
### Step 3: Ambassador Program Design
Ambassadors are your best users who promote the product without being paid to.
Prerequisites before launching:
- 50+ active community members
- Clear product value for ambassadors (early access, credits, direct line to founders)
- Bandwidth to support ambassadors with content, assets, and attention
Ambassador program structure:
```markdown
## [Product] Ambassador Program
**Who qualifies:**
- Active community member for [N] months
- Has shared the product publicly at least once
- [Role fit — e.g., developer, team lead, OSS contributor]
**What ambassadors get:**
- Early access to features
- [Product] credits / extended plan
- Direct Slack channel with team
- Speaking opportunities at [Product] events
- LinkedIn / Twitter recognition
**What ambassadors do:**
- Share honest product experiences publicly
- Run or attend 1 local event / meetup per quarter
- Provide product feedback monthly
- Help community members with questions
**Application:**
[Simple form — 3 questions max]
```
### Step 4: Community Flywheel
Design the community flywheel specific to this product:
```
VALUE (product solves a real problem)
↓
MEMBERS join community
↓
CONNECTIONS form between members (peer relationships)
↓
CONTRIBUTIONS increase (questions, answers, code, content)
↓
BETTER PRODUCT from community feedback
↓
MORE VALUE created
↓ (loop)
```
Identify the current weakest link in the flywheel. That's the one to fix.
### Step 5: Produce Community Playbook
```markdown
# Community Playbook — [Product Name]
**Current stage:** [Seed/Momentum/Flywheel]
**Primary platform:** [Discord/Slack/GitHub/Reddit]
## Platform Structure
[channel list and purpose]
## Community Rules
[3-5 rules, enforced consistently]
## Onboarding Flow
New member → [Step 1] → [Step 2] → [engaged in 7 days]
## Contributor Path
Lurker → [trigger] → First contribution → Regular contributor
## Ambassador Program
[if applicable — criteria, benefits, expectations]
## Response SLAs
- Help questions: [N] hours
- Bug reports: [N] hours
- PR review: [N] hours
- Feature requests: Acknowledged [N] days, responded to in roadmap cycle
## Community Health Metrics
- Weekly active members (target: 10% of total)
- Questions answered by community (not team) (target: 60%+)
- Contribution rate (% of members who contribute code/content) (target: 5%+)
- Member churn rate (inactive 30 days) (target: <20%/month)
## Weekly Community Ops (30 min/week)
[ ] Respond to all unanswered questions
[ ] Highlight one community member or contribution
[ ] Share one piece of product news or behind-the-scenes
[ ] Check for new GitHub issues — label and respond
```
## Delivery
Produce the complete community playbook and GitHub health checklist. Every section should be immediately actionable — not theory.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
If output exceeds 40 lines, delegate to /atlas-report.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供完整的开源社区建设方法论,涵盖 Discord/Slack 架构、贡献者引导、大使计划、社区飞轮设计
评分依据
触发词精准完整,覆盖多种变体,边界清晰
评分依据
结构清晰,分步骤展开,每步有明确目标和出口条件
评分依据
提供具体可执行的工具和方法,参数明确
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。