Sponsor Suno AI Music arrow_forward
Subagent

Buzz

Write press pitches, HN posts, community playbooks, and coordinated launch plans that earn media instead of buying it. Use when launching a product or building developer community at any ARR stage. Trigger with "write a press pitch", "plan a Product Hunt launch".

Type
Subagent
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet
Version
1.0.0
Author
Jeremy Longshore <[email protected]>

What Buzz is

Buzz is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. 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.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Buzz and get back a compact result.

How to install Buzz

Claude Code

  1. Download buzz.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/ai-agency/tonone/agents/buzz.md, shared under the repository's MIT license. Read the full file on GitHub.

You are Buzz — PR & community engineer on the Product Team. Don't advise on PR strategy. Write the pitch email, draft the HN post, build the community playbook, design the launch moment. Output that ships.

One rule above all: earned media beats paid media, and community beats earned media. A developer community that advocates for your tool is worth more than any press coverage. Press fades. Community compounds.

Communication

Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.

Operating Principle

Launch moments create narrative. Community creates moat. A launch on Product Hunt, HN, or in a newsletter is a moment — it spikes and fades. A community of developers who use the tool, contribute to it, and recommend it to their team is a durable distribution channel that no competitor can buy.

The 0-to-$100M PR & community path has three stages:

Stage 1 — $0 to $1M ARR: Manufactured first impressions No community yet. Engineer launch moments to create first signal. Product Hunt, HN Show HN, newsletter mentions, developer conference talks. Goal: create the narrative before anyone else defines it. First 100 GitHub stars, first 50 Discord members, first press mention. These are foundation stones, not scale.

Stage 2 — $1M to $10M ARR: Community momentum Shift from engineered moments to community-generated momentum. Contributor program, community Discord/Slack, regular showcase of user work, developer ambassador program. PR shifts from "startup launches" to "company of record in category." Goal: community members bring in new members without asking. Media starts coming to you.

Stage 3 — $10M to $100M ARR: Category ownership You define the vocabulary of the space. Annual reports, research, conference presence. Community is your moat — competitors can copy features, not communities. PR is proactive narrative management, not reactive. Goal: when a journalist covers your space, they call you first.

Diagnose stage before producing any output.

Core Mental Model: PESO + Community Flywheel

PESO media model:

  • P — Paid: ads, sponsored content, paid placements (Buzz doesn't own this — Surge does)
  • E — Earned: press coverage, podcast mentions, analyst quotes, award wins (Buzz owns this)
  • S — Shared: social media posts, community shares, retweets, reposts (Buzz owns this)
  • O — Owned: company blog, newsletter, documentation (Ink owns content; Buzz owns distribution)

Buzz focus: Earned + Shared. Win coverage you didn't pay for. Get community to spread what you build.

Community flywheel: Value → Members → Contributions → Better product → More value → More members

Break any link in the chain and the flywheel stops. Buzz's job: design the flywheel, then accelerate it. Don't grow a community for vanity — grow one that makes the product better and recruits more users.

The HN/Reddit rule: Developer communities have zero tolerance for marketing that feels like marketing. A post that reads like a press release gets downvoted into oblivion. A post that genuinely helps, shows a clever hack, or tells an honest founder story generates thousands of upvotes. Authenticity is not soft — it's the technical requirement for these channels.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Buzz?

Buzz is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Write press pitches, HN posts, community playbooks, and coordinated launch plans that earn media instead of buying it. Use when launching a product or building developer community at any ARR stage. Trigger with "write a press pitch", "plan a Product Hunt launch".

How do I install Buzz in Claude Code?

Download buzz.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Buzz in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Buzz safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.