[omh] Hermes adaptation for measurable performance-goal execution.
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 16 of 19 test cases with the skill, and 8 of 19 without it.
Without skill41%
With skill86%
Checks it passed that the model alone missed
Identifies that the benchmark command input is missing
Lists category as optimization and phase as measurement
Provides an implementation summary for the throughput changes
and 12 more in the full report
10 fixed9 passed either way3 still failing0 broke
Pass-rate lift
+45 pp
Tokens
+13%
Agent turns
0%
Response time
-47%
Model gemini-3.6-flashMeasured 8/19/2026v219 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
We planned the optimization of our search index lookup using `cargo bench --bench search`. The code edits were drafted but the benchmark suite has not been executed on the target hardware yet. What is the execution status?
What was checked, without and with the skill
Checked
Without skill
With skill
Marks the benchmark evidence status as not_observed or not_available
Missed
Passed
Identifies the smallest next verification step instead of claiming complete results
Passed
Passed
case-09 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md105 linessingle file
Performance Goal
This is a Hermes-native performance-goal workflow skill.
Why This Exists
performance-goal exists to keep optimization work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
Do Not Use When
The ask is to find where performance problems are, or to fix multiple unscoped hotspots across domains; use ultraperf.
Examples
Good example:
Prompt: performance-goal: benchmark recommendation latency, optimize hot paths safely, and prove no regressions.
Expected behavior: Create a measurement-led optimization loop with baseline, change, verification, and regression evidence.
Why: The request is performance optimization and needs measured before/after proof.
Bad example:
Prompt: performance-goal: treat casual chat or unaccepted work as if this workflow already produced verified results.
Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing performance-goal.
Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
Completion Checklist
Confirm the workflow target, evidence boundary, and stop condition are named.
Report which outputs are prepared, observed, blocked, or missing.
Name the smallest next verification or handoff instead of claiming completion from narration.
Recovery Notes
If required context is missing, ask one blocking question or route back to the narrower workflow.
If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
Workflow Lane
Current lane: Intent -> plan (oh-my-hermes, meta-router, deep-interview, context, plan, ralplan, codebase-onboarding, codegraph-refresh, +4 more) - clarify, plan, ship, or loop goals.