SKILLEMALL.ai
GitHub ↗ RU Sign in

CB ulw-work

[omh] Accepted plan awaiting implementation: split it into disjoint parallel lanes with per-lane acceptance criteria, verification commands, and owners; prevents two lanes editing the same file. Aliases: ulw. Use when the user says: ultrawork, parallel work, parallel implementation, parallel then integrate, high throughput, coding team, coordinated workers, finish until done.

rlaope/oh-my-hermes Hermes author: rlaope 2 files body ≈ 5 132 tokens Open the sourcegithub.com↗ analyzed 14 h ago

[omh] Accepted plan awaiting implementation: split it into disjoint parallel lanes with per-lane acceptance criteria, verification commands, and owners…

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

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
68
Run on models
none yet
Process rating
B
68/100
Nearly there
Running it twice w 4
30
Result and completion w 14
40
Failures and branches w 10
50
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: oh-my-hermes

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 Concealment en-hide-from-user SKILL.md:31
    Instruction to hide actions from the user (negated — the text forbids it)
    - The user expects Hermes to secretly execute coding lanes instead of preparing explicit selected-runtime handoffs.
    negated

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

Against the Agent Skills spec

  • warning description-long-hermes description is 378 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning body-long SKILL.md body ≈ 5132 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 68/100

  • 30Running it twice. 7 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5132 tokens
  • 100Steps. 93 steps
  • 100When it triggers. States when to use and when not to
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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
  • -5TODO / placeholder text left in the skill
  • +2Single-language instructions
  • +3Description length 378: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 93 items
  • +4Has examples (0 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

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