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

Omh Buzz

by rlaope in rlaope/oh-my-hermes

[omh] Buzz community agent setup or relay trouble: connect and operate Hermes as a native Buzz community agent, deliver local media with verified relay receipts, or diagnose a self-hosted Buzz relay…

MITAuto-check passed

Install Omh Buzz

skills CLI
$ npx skills add rlaope/oh-my-hermes --skill omh-buzz -a claude-code

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

GitHub CLI
$ gh skill install rlaope/oh-my-hermes omh-buzz --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/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-buzz .claude/skills/omh-buzz && 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
omh-buzz
GitHub stars
3.2k
Token cost
~2k tokens
SKILL.md length
1,000 words
Files
4 (incl. references)
Skills in repo
143
Repo updated
First seen
Licence
MIT

At a glance

[omh] Buzz community agent setup or relay trouble: connect and operate Hermes as a native Buzz community agent, deliver local media with verified relay receipts, or diagnose a self-hosted Buzz relay…

  • The user says: connect Hermes to Buzz
  • SKILL.md covers Why This Exists, Do Not Use When, Examples and Completion Checklist, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Buzz community agent

What it does

Omh Buzz is an agent skill from rlaope/oh-my-hermes. [omh] Buzz community agent setup or relay trouble: connect and operate Hermes as a native Buzz community agent, deliver local media with verified relay receipts, or diagnose a self-hosted Buzz relay without inventing transport evidence. Aliases: omh-buzz. Use when the user says: connect Hermes to Buzz, Buzz community agent, Buzz gateway setup, Buzz media attachment, Buzz relay self-hosting, Buzz connection diagnostics, 버즈 커뮤니티 연결, Buzz 메시지 첨부.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/media.md`, `references/self-host.md` and `references/setup.md`).

The repository describes itself as: All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages. The licence is MIT.

When your agent uses it

  • The user says: connect Hermes to Buzz
  • Buzz community agent
  • Buzz gateway setup
  • Buzz media attachment

Example prompts

  • “/omh-buzz”

Requirements

  • Docker

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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

Omh Buzz loads about 2k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 114 tokens; SKILL.md has 1,000 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~114
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.8k

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 passed

The automated check found no risky patterns in SKILL.md.

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 rlaope/oh-my-hermes at commit 41de9dc, republished under its MIT licence (© rlaope). 1,000 words, ~1,976 tokens.

Download SKILL.mdSave it as .claude/skills/omh-buzz/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
omh-buzz
description
[omh] Buzz community agent setup or relay trouble: connect and operate Hermes as a native Buzz community agent, deliver local media with verified relay receipts, or diagnose a self-hosted Buzz relay without inventing transport evidence. Aliases: omh-buzz. Use when the user says: connect Hermes to Buzz, Buzz community agent, Buzz gateway setup, Buzz media attachment, Buzz relay self-hosting, Buzz connection diagnostics, 버즈 커뮤니티 연결, Buzz 메시지 첨부.

Buzz

This is a Hermes-native buzz workflow skill.

Why This Exists

Hermes already owns the Buzz transport, but users need one discoverable OMH entry point that safely selects setup, attachment, or self-host operations and reports only the evidence actually observed.

Do Not Use When

  • The user wants a Buzz-managed ACP runtime rather than Hermes' native Buzz gateway.
  • The request is general media editing with no Buzz delivery target.
  • The request is generic Docker or Nostr advice unrelated to a Buzz relay.
  • The user is only asking whether OMH supports Buzz, with no request to run the workflow.

Examples

Good example:

  • Prompt: Connect this Hermes gateway to my Buzz community and verify one inbound and outbound message.
  • Expected behavior: Load the setup reference, collect the relay and membership inputs without exposing the private key, use Hermes' guided gateway setup, then report each observed verification stage.
  • Why: The request names the native gateway task and an observable end-to-end stop condition.

Bad example:

  • Prompt: Write a generic Nostr relay from scratch for OMH.
  • Expected behavior: Route to planning or coding rather than presenting that transport as part of omh-buzz.
  • Why: OMH reuses Hermes' native Buzz adapter and does not own a second Nostr transport.

Completion Checklist

  • Exactly one of setup, media, or self-host is selected from request meaning; no internal lane is public.
  • Secrets remain out of argv, logs, rendered output, and workflow artifacts.
  • Configuration, process, relay, event acceptance, subscription, and client rendering are separate claims.
  • Any state-changing self-host command remains user-driven and has an explicit rollback or backup boundary.
  • The final answer names what was observed, what remains unobserved, and the next smallest proof action.

Recovery Notes

  • If the Buzz CLI is missing, stop at installation guidance and do not claim gateway readiness.
  • If relay authentication fails, separate membership, identity, and NIP-42 evidence before changing config.
  • If a send receipt is malformed or lacks an event id, report ambiguous delivery and do not auto-retry.
  • If self-host readiness is green but media fails, inspect MinIO and disk separately from relay readiness.

Workflow Lane

  • Current lane: Automation and status (achievements, workspace-audit, production-audit, live-incident-response, automation-blueprint, github-event-ops, github-issue-intake, buzz, +39 more) - schedules, status, health, and ops review.
  • If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.

Choose One Internal Lane

omh-buzz is the only public skill. Choose exactly one reference from the request's meaning after this skill is selected:

  • Load references/setup.md to connect or repair Hermes' native Buzz gateway.
  • Load references/media.md to deliver a local attachment to the active Buzz conversation and report staged delivery evidence.
  • Load references/self-host.md to inspect or guide a self-hosted Buzz relay.

Do not expose these references as separate skills and do not select them with a hard-coded keyword branch. If the request genuinely spans lanes, start with setup/readiness, then load only the next reference required by observed state.

Ownership Boundary

Hermes owns the native Buzz transport, authentication, inbound subscriptions, and outbound CLI invocation. OMH owns this operator workflow, the buzz platform identity layered over source hermes, safe evidence boundaries, and progressive guidance. Block's Buzz relay and CLI own their runtime semantics.

Use When

Use when the user wants to configure or troubleshoot Hermes' native Buzz gateway, attach local media to the active Buzz conversation, or inspect a self-hosted Buzz relay. Select the setup, media, or self-host reference from the request's meaning after this single public skill is selected.

Strong routing signals: `connect Hermes to Buzz`, `Buzz community agent`, `Buzz gateway setup`, `Buzz media attachment`, `Buzz relay self-hosting`, `Buzz connection diagnostics`, `버즈 커뮤니티 연결`, `Buzz 메시지 첨부`
Show full SKILL.md (401 more words)Show less

Catalog Metadata

Category: operator Phase: messaging-integration Hermes role: tracker Quality tier: evidence-gated Reasoning demand: light

Quality bar:

  • Name the workflow target, constraints, validation evidence, and stop condition.
  • Separate Hermes guidance from executor or wrapper behavior unless evidence proves the step happened.

Handoff policy:

Operate through Hermes' native Buzz adapter and official Buzz surfaces. Keep state-changing self-host commands user-driven and delegate repository code changes only when the user explicitly asks for them.

Required inputs:

  • Buzz task: gateway setup, media delivery, or self-host diagnosis
  • target Hermes home or active Buzz conversation
  • observable stop condition

Expected outputs:

  • selected Buzz workflow lane
  • bounded setup or diagnostic evidence
  • observed delivery stage or explicit unobserved boundary

Artifact expectations:

  • redacted Buzz readiness summary when setup is inspected
  • delivery receipt with accepted event id when media is sent
  • self-host failure-tree evidence when relay health is diagnosed

Safety rules:

  • Reuse Hermes' native Buzz transport; do not implement or imply an OMH-owned Nostr transport.
  • Never print, persist in workflow artifacts, or place the Buzz private key in argv or shell history.
  • Do not treat CLI presence, configuration presence, or a prepared command as live relay readiness.
  • Do not claim message delivery without accepted=true and a non-empty event id from the send receipt.
  • Guide, don't drive state-changing self-host operations unless the user explicitly approves each action.

Runtime Evidence

Record observed delegation results; otherwise return not_available or not_observed. Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.

  • Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes. Preserve workflow intent and stop conditions; verify before claiming completion. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.

Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.

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

Files

SKILL.md and 3 other files (references) in skills/omh-buzz of rlaope/oh-my-hermes.

  • SKILL.md
  • references/media.md
  • references/self-host.md
  • references/setup.md

Open the folder on GitHubat commit 41de9dc

Compare with similar skills

Omh Buzz 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.

Omh Buzz compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Omh Buzz this skillrlaope/oh-my-hermes3.2k—~2kAutomated safety check: PassMIT
ConnectComposioHQ/awesome-claude-skills77k3 repos~987Automated safety check: PassNone
Node Connectopenclaw/openclaw392k—~1.6kAutomated safety check: PassMIT
Openwork Connectdifferent-ai/openwork24k—~370Automated safety check: PassCustom licence
Connection Auth Rulessickn33/agentic-awesome-skills47k1 repos~2.1kAutomated safety check: PassMIT
Connections Optimizeraffaan-m/ECC276k2 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Connect

    ComposioHQ/awesome-claude-skills

    Connect Claude to any app. An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~987 tokens
    Productivity & AutomationAuto-check passed

  • Node Connect

    openclaw/openclaw

    Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.

    392k GitHub stars~1.6k tokensUpdated today
    MobileAuto-check passed

  • Openwork Connect

    different-ai/openwork

    Search and use the skills, MCP connections, and connected services available through the user's OpenWork organization.

    24k GitHub stars~370 tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Connection Auth Rules

    sickn33/agentic-awesome-skills

    Build a Connection Auth Rules for a Monte Carlo connection type.

    47k GitHub starsUsed in 1 repo~2.1k tokens
    Backend & APIsAuto-check passed

  • Connections Optimizer

    affaan-m/ECC

    Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach drafted in the user's real voice.

    276k GitHub starsUsed in 2 repos~1.4k tokens
    Auto-check passed

  • Connections Optimizer

    affaan-m/ECC

    レビュー優先の整理、フォロー/追加の推薦、ユーザーの実際の声で書かれたチャネル別ウォームアウトリーチのドラフトを通じて、ユーザーのXとLinkedInネットワークを再編成します。フォローリストを整理したい、現在の優先事項に向けて成長したい、または高品質な関係を中心にソーシャルグラフのバランスを取り直したい場合に使用します。

    276k GitHub stars~860 tokensUpdated 4 days ago
    Auto-check passed

More from rlaope/oh-my-hermes

All 143 skills in this repo

  • Omh Accessibility Audit

    rlaope/oh-my-hermes

    [omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.

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

  • Omh Agent Evaluation

    rlaope/oh-my-hermes

    [omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics.

    3.2k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Omh Agent Instructions

    rlaope/oh-my-hermes

    [omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or…

    3.2k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Omh Agent Ops Review

    rlaope/oh-my-hermes

    [omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.

    3.2k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Omh AI Slop Cleaner

    rlaope/oh-my-hermes

    [omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical.

    3.2k GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Omh App Debugging

    rlaope/oh-my-hermes

    [omh] Application code misbehaves -- a wrong value, a flaky test, a lost update: reproduce it first, form competing hypotheses, discriminate them with the cheapest observation, and only then fix the…

    3.2k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Questions about Omh Buzz

What does Omh Buzz do?

[omh] Buzz community agent setup or relay trouble: connect and operate Hermes as a native Buzz community agent, deliver local media with verified relay receipts, or diagnose a self-hosted Buzz relay…. Omh Buzz is an agent skill from rlaope/oh-my-hermes. [omh] Buzz community agent setup or relay trouble: connect and operate Hermes as a native Buzz community agent, deliver local media with verified relay receipts, or diagnose a self-hosted Buzz relay without inventing transport evidence.

When should I use Omh Buzz?

Omh Buzz fits situations like: the user says: connect Hermes to Buzz; buzz community agent; buzz gateway setup; buzz media attachment.

How do I install Omh Buzz in Claude Code?

Run `npx skills add rlaope/oh-my-hermes --skill omh-buzz -a claude-code`. Or copy the skill folder (skills/omh-buzz in rlaope/oh-my-hermes) into .claude/skills/omh-buzz in your project. Claude Code loads it when a task matches its description.

How do I install Omh Buzz in Codex?

Run `npx skills add rlaope/oh-my-hermes --skill omh-buzz -a codex`. Or copy the skill folder (skills/omh-buzz in rlaope/oh-my-hermes) into .agents/skills/omh-buzz in your project. Codex loads it when a task matches its description.

Can I use Omh Buzz 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 rlaope/oh-my-hermes --skill omh-buzz -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omh-buzz, .gemini/skills/omh-buzz, .github/skills/omh-buzz and .opencode/skills/omh-buzz in your project.

What does Omh Buzz need to run?

SKILL.md names no scripts, command-line tools or credentials: Omh Buzz is instructions for the agent only. Our summary lists: Docker.

Does Omh Buzz 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 Omh Buzz safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omh Buzz use?

Omh Buzz is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Omh Buzz use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Omh Buzz?

Skills that share tags, products or a category with Omh Buzz: Connect (ComposioHQ/awesome-claude-skills, 77k stars), Node Connect (openclaw/openclaw, 392k stars), Openwork Connect (different-ai/openwork, 24k stars) and Connection Auth Rules (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omh Buzz?

rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,233 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 8, 2026.

Source: rlaope/oh-my-hermes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.