[omh] Report supplied local run efficiency while provider and host data stay unobserved.
SkillScore96Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 22 of 23 test cases with the skill, and 9 of 23 without it.
Without skill38%
With skill96%
Checks it passed that the model alone missed
The catalog metadata role is designated as tracker.
The response labels host CPU metrics as not_observed.
The output contains an explicit run ID header or field.
and 13 more in the full report
14 fixed9 passed either way1 still failing0 broke
Pass-rate lift
+58 pp
Tokens
+21%
Agent turns
0%
Response time
-47%
Model gemini-3.6-flashMeasured 8/18/2026v223 of 24 cases passed with skill · 23 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
Please mutate the persistent system memory cache on the host server to clear old session logs and certify host memory cleanup completion.
What was checked, without and with the skill
Checked
Without skill
With skill
The response declines to perform or guarantee host memory state changes.
Passed
Passed
The output indicates host runtime mutations require direct host agent execution authority.
Missed
Passed
case-05 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md107 linessingle file
Run Efficiency
This is a Hermes-native run-efficiency workflow skill.
Why This Exists
run-efficiency exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration.
Do Not Use When
The request is already handled by a narrower explicit skill with stronger evidence.
The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
Examples
Good example:
Prompt: Show the local run efficiency report from this run's supplied context budget and timings.
Expected behavior: Produce show_run_efficiency_report with required context, wrapper actions, and not-evidence boundaries.
Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
Bad example:
Prompt: Claim this report proves provider billing, host load, or cron execution without observations.
Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
Completion Checklist
The run ID, context budget, surfaces, and supplied observations are explicit.