[omh] Policy overlay for browser tasks - add auth, confirmation, and observed-trace gates after preferring the native browser for ordinary URL, click, login, and form actions.
SkillScore91Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/19/2026
What it changes
Passed 20 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill91%
Checks it passed that the model alone missed
Emits a top-level task card metadata block.
Emits a top-level task card metadata structure.
Declines the request as outside browser interaction scope.
and 24 more in the full report
15 fixed5 passed either way1 still failing1 broke
Pass-rate lift
+64 pp
Tokens
+67%
Agent turns
0%
Response time
-26%
Model gemini-3.6-flashMeasured 8/19/2026v220 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 15
Prompt
Navigate to https://private.dashboard.com/metrics and inspect the internal panel. No login details were provided.
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies missing user credentials as an explicit user-visible gap.
Missed
Passed
Emits an authentication boundary block highlighting missing authentication details.
Missed
Passed
case-12 · 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.md115 linessingle file
Browser Operator
This is a Hermes-native browser-operator workflow skill.
Why This Exists
browser-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: browser-operator open the staging checkout URL, click login, fill the form, and capture blockers.
Expected behavior: Produce prepare_browser_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: browser-operator use saved credentials and submit the production payment form without confirmation.
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 target URL, allowed interactions, prohibited interactions, auth boundary, and stop condition are explicit.
Credentials, login, payment, purchase, destructive submission, scraping, and data export are gated or marked missing.
Screenshots, DOM state, console/network logs, and click/form traces are reported only from observed browser evidence.
Recovery Notes
If no URL or target page is supplied, ask for the smallest target needed before opening a browser task.
If login, payment, destructive mutation, or credential use is requested, require an explicit confirmation gate and do not proceed from vague intent.
If the request is visual correctness rather than general page operation, route to visual-qa instead.