[omh] Policy overlay for live lookups - add provider, freshness, units, and source-quality gates after preferring native live-data tools for ordinary weather, finance, sports, maps, and time-zone requests.
SkillScore86Maintained
Automatic
◆Personal Assistant pack
Last verified 8/18/2026
What it changes
Passed 18 of 21 test cases with the skill, and 3 of 21 without it.
Without skill14%
With skill86%
Checks it passed that the model alone missed
Outputs live_info_task_card/v1 as metadata wrapper
Defines 2-hour recency window in freshness_boundary/v1
Routes to toolbelt-readiness for missing provider setup
and 26 more in the full report
16 fixed3 passed either way3 still failing0 broke
Pass-rate lift
+73 pp
Tokens
+33%
Agent turns
0%
Response time
-27%
Model gemini-3.6-flashMeasured 8/18/2026v319 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
Prepare a live information lookup card for current time in Sydney relative to UTC.
Defines time-zone domain context within live_info_scope/v1
Missed
Passed
case-14 · 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.md114 linessingle file
Live Info Operator
This is a Hermes-native live-info-operator workflow skill.
Why This Exists
live-info-operator 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: live-info-operator check today's Seoul weather with freshness, units, and provider boundaries before answering.
Expected behavior: Produce prepare_live_info_operator_card 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: live-info-operator invent the latest stock price without provider evidence or timestamp.
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
Domain, location or symbol, time window, provider preference, freshness, units, and stop condition are explicit.
Provider setup, API access, source quality, stale data, and missing location/symbol decisions are gated or marked missing.
Weather, price, score, exchange-rate, time-zone, map, place, and traffic facts are reported only from observed provider evidence.
Recovery Notes
If the provider, plugin, API key, or connector is missing, route to toolbelt-readiness before preparing result claims.
If the request asks for citations, best practices, docs, or broad current-source synthesis, route to research instead.
If the request would create, update, invite, send, or mutate external provider state, route to connector-operator instead.