SKILLEMALL.ai
GitHub ↗ RU Sign in

BB omh-buzz

[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 메시지 첨부.

rlaope/oh-my-hermes Hermes author: rlaope 4 files body ≈ 1 847 tokens Open the sourcegithub.com↗ analyzed 14 h ago

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

As a process B 73/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting

ProcedureAI and agentstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
B
73/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
Result and completion w 14
40
the three weakest of ten parameters · all ten

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 447 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)

Process rating: all ten parameters 73/100

  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 42 steps
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 1 branches, has a failure section
  • 100Execution cost. Instruction body is 1847 tokens
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 447: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 42 items
  • +4Has examples (0 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.