SKILLEMALL.ai

BC omh-show-reel

[omh] Motion showcase to make: produce a source-grounded product film with audience-specific concepts, segment direction, authored motion, measured locale/export QA and reproducible source delivery. Use when the user says: show-reel, show reel, showreel, product showcase video, animated product film, motion showcase, animated portfolio, launch film.

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

[omh] Motion showcase to make: produce a source-grounded product film with audience-specific concepts, segment direction, authored motion, measured…

As a process C 63/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting

GeneratorMedia and videotype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
99
Quality 40%
83
Run on models
none yet
Process rating
C
63/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
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.
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 Dangerous commands cmd-shell-rc references/craft-audio.md:21
    Writes to a shell startup file (quoted — discussed, not commanded)
    3. Save it in the shell config: `echo 'export ELEVENLABS_API_KEY="sk_..."' >> ~/.zshrc && source ~/.zshrc`, or as `ELEVENLABS_API_KEY=sk_...` in `.env` in the project folder
    quoted

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

Against the Agent Skills spec

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

Process rating: all ten parameters 63/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 46 steps
  • 100When it triggers. States when to use and when not to
  • 100Execution cost. Instruction body is 2480 tokens
  • 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
  • +2Single-language instructions
  • +3Description length 351: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 46 items
  • +4Has examples (0 code blocks)
  • +4Reference files are cited in the instructions (9 of 21)
  • +1License stated

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