SKILLEMALL.ai
GitHub ↗ RU Sign in

CB omh-routing

[omh] Choosing among OMH skills for a request: router guidance for using oh-my-hermes workflow skills inside Hermes Agent.

rlaope/oh-my-hermes Hermes author: rlaope 13 files body ≈ 3 292 tokens Open the sourcegithub.com↗ analyzed 14 h ago

[omh] Choosing among OMH skills for a request: router guidance for using oh-my-hermes workflow skills inside Hermes Agent.

As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureSoftware developmentAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
71
Run on models
none yet
Process rating
B
65/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Risky intent intent-offensive-security references/workflow-registry.md:100
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
    - `adversarial-consensus`: `adversarial-consensus`, `$adversarial-consensus`, `adversarial planning`, `adversarial plan review`, `red team this plan`, `red-team this plan`, `red team the proposal`, `m
    quoted

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

Against the Agent Skills spec

  • warning description-long-hermes description is 122 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill

Process rating: all ten parameters 65/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 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
  • 100Steps. 60 steps
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 3292 tokens
  • low 16 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 122: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 60 items
  • +4Has examples (0 code blocks)
  • +4Reference files are cited in the instructions (9 of 12)
  • +1License stated

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