New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Buzz Community

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health.

MITAuto-check: notesDevelopment

Install Buzz Community

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-community -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace buzz-community --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/buzz-community .claude/skills/buzz-community && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
buzz-community
GitHub stars
2.8k
Token cost
~1.5k tokens
SKILL.md length
298 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health.

  • Works in 6 steps: Community Stage Assessment → Platform Design → Contributor Onboarding → …
  • Asked to build a community
  • SKILL.md covers Steps and Delivery
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Buzz Community is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Open source maintenance. It works with Discord, GitHub and Slack. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asked to build a community
  • Grow our Discord
  • Improve contributor experience
  • Design a developer ambassador program

Example prompts

  • “build a community”
  • “grow our Discord”
  • “improve contributor experience”
  • “/buzz-community”

Requirements

  • Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Community Stage Assessment
  2. Platform Design
  3. Contributor Onboarding
  4. Ambassador Program Design
  5. Community Flywheel
  6. Produce Community Playbook

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Glob
    • Grep
    • WebFetch
    • WebSearch
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Buzz Community loads about 1.5k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 298 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 298 words, ~1,486 tokens.

Download SKILL.mdSave it as .claude/skills/buzz-community/SKILL.md (or your agent's skills folder).
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.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/ai-agency/tonone/skills/buzz-community of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

Buzz Community next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Buzz Community compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Buzz Community this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.5kAutomated safety check: NotesMIT
Community Buildingmanojbajaj95/claude-gtm-plugin105—~4.5kAutomated safety check: PassMIT
Openloomi Connectorsmelandlabs/openloomi1k—~3.3kAutomated safety check: PassApache-2.0
Chat SDKdatabuddy-analytics/Databuddy1.2k—~2.6kAutomated safety check: PassAGPL-3.0
Eunomia Community Radareunomia-bpf/eunomia.dev236—~2.5kAutomated safety check: PassMIT
Latchkeyimbue-ai/latchkey130—~1.3kAutomated safety check: PassMIT

Similar skills

  • Community Building

    manojbajaj95/claude-gtm-plugin

    Build and grow online communities across all platforms and contexts — from developer/B2B communities (Discord, Slack, Circle, Discourse) to social communities (Twitter/X, Reddit, Farcaster) to…

    105 GitHub stars~4.5k tokensUpdated 23 days ago
    DevelopmentAuto-check passed

  • Openloomi Connectors

    melandlabs/openloomi

    openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…

    1k GitHub stars~3.3k tokensUpdated 17 days ago
    Productivity & AutomationAuto-check passed

  • Chat SDK

    databuddy-analytics/Databuddy

    Build multi-platform chat bots with Chat SDK (chat npm package).

    1.2k GitHub stars~2.6k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Eunomia Community Radar

    eunomia-bpf/eunomia.dev

    Monitor approved eBPF, Linux, observability, and AI-infrastructure communities through watchlist-opted-in read-only Slack archives plus ordinary visible browser UI, turn the strongest daily…

    236 GitHub stars~2.5k tokensUpdated today
    Knowledge ManagementAuto-check passed

  • Latchkey

    imbue-ai/latchkey

    Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.

    130 GitHub stars~1.3k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • Frontmcp Channels

    agentfront/frontmcp

    A skill your agent uses when pushing real-time notifications or events into Claude Code (or another MCP client) sessions, or building two-way chat bridges.

    146 GitHub stars~3.7k tokensUpdated today
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Buzz Community

What does Buzz Community do?

Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Buzz Community is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health.

When should I use Buzz Community?

Buzz Community fits situations like: asked to build a community; grow our Discord; improve contributor experience; design a developer ambassador program.

How do I install Buzz Community in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-community -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/buzz-community in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/buzz-community in your project. Claude Code loads it when a task matches its description.

How do I install Buzz Community in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-community -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/buzz-community in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/buzz-community in your project. Codex loads it when a task matches its description.

Can I use Buzz Community in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill buzz-community -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/buzz-community, .gemini/skills/buzz-community, .github/skills/buzz-community and .opencode/skills/buzz-community in your project.

What does Buzz Community need to run?

SKILL.md names no scripts, command-line tools or credentials: Buzz Community is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion.

Does Buzz Community access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Buzz Community safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Buzz Community use?

Buzz Community is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Buzz Community use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Buzz Community?

Skills that share tags, products or a category with Buzz Community: Community Building (manojbajaj95/claude-gtm-plugin, 105 stars), Openloomi Connectors (melandlabs/openloomi, 1k stars), Chat SDK (databuddy-analytics/Databuddy, 1.2k stars) and Eunomia Community Radar (eunomia-bpf/eunomia.dev, 236 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Buzz Community?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.