SKILLEMALL.ai
GitHub ↗ RU Sign in

BB omh-commit-pr-authoring

[omh] Commit message or pull-request body to write for a change: draft it in the repository's own convention, with `Tested:` listing only commands observed to run and everything prepared but not run under `Not-tested:`. Use when the user says: commit-pr-authoring, commit message, commit messages, write the commit message, draft the commit message, commit body, squash message, pr body.

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

[omh] Commit message or pull-request body to write for a change: draft it in the repository's own convention, with Tested: listing only commands observed to…

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

GeneratorGitHubSoftware developmenttype 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
67/100
Nearly there
Result and completion w 14
0
Failures and branches w 10
0
Running it twice w 4
30
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: omh-commit-pr-authoring (rlaope/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.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

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

Process rating: all ten parameters 67/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 33 mutating operations with no state check
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 48 steps
  • 100When it triggers. States when to use and when not to
  • 100Execution cost. Instruction body is 2132 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 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 387: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 48 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: 83.