SKILLEMALL.ai
GitHub ↗ RU Sign in

BB ulw-qa

[omh] Hostile scenario testing: adversarial QA and fix loops. Use when the user says: ultraqa, adversarial qa, hostile scenarios, e2e qa, real-world qa, qa scenario, release qa, 敵対的QA.

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

[omh] Hostile scenario testing: adversarial QA and fix loops.

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

AnalyzerSoftware developmentAI and agentsPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
B
68/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

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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

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

Process rating: all ten parameters 68/100

  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 4 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) that frontmatter does not declare
  • 60Consistency. The Hermes dialect needs category and tags
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 40 steps
  • 100When it triggers. States when to use and when not to
  • 100Execution cost. Instruction body is 2487 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
  • -5TODO / placeholder text left in the skill
  • +2Single-language instructions
  • +3Description length 184: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +1License stated

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