[omh] Terse voice and mobile-style requests - turn short spoken-style asks into clarify, plan, status, handoff, or confirmation actions.
SkillScore82Maintained
Automatic
◆Personal Assistant pack
Last verified 8/19/2026
What it changes
Passed 18 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill82%
Checks it passed that the model alone missed
Marks warehouse transaction as not_observed
Does not claim CDN cache invalidation occurred
Marks actual process termination as not_observed
and 17 more in the full report
14 fixed4 passed either way2 still failing2 broke
Pass-rate lift
+55 pp
Tokens
+74%
Agent turns
0%
Response time
-13%
Model gemini-3.6-flashMeasured 8/19/2026v218 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
Dictated request: 'check main branch build status'. Produce the voice operator response.
What was checked, without and with the skill
Checked
Without skill
With skill
Outlines immediate readable status review action
Passed
Passed
Marks CI runner execution and log fetch as not_observed until verified
Missed
Passed
case-18 · 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.md107 linessingle file
Voice Operator
This is a Hermes-native voice-operator workflow skill.
Why This Exists
voice-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: voice-operator 'release before lunch, check risky parts' from mobile.
Expected behavior: Produce prepare_voice_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: voice-operator assume the user approved a destructive action from a vague voice note.
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 short-input or voice-like request is clarified enough to avoid accidental action.
The next action is readable, reversible when possible, and confirmation-gated when risky.
Delivery, notification, or platform behavior is not claimed without wrapper evidence.
Recovery Notes
If transcript confidence or intent is weak, ask one short clarification before action.
If platform delivery is unavailable, keep the response in chat and mark delivery not_observed.