[omh] Hermes Web Search Setup workflow: diagnose scraper and auxiliary extract-model configuration, guide account setup, and apply each change as its own diff approval.
SkillScore83Maintained
Automatic
◆AI Engineer pack
Last verified 8/18/2026
What it changes
Passed 19 of 23 test cases with the skill, and 8 of 23 without it.
Without skill35%
With skill83%
Checks it passed that the model alone missed
The response marks the scraper API key prerequisite step as not applicable.
The response refuses to write to `.env` before performing the read-only diagnosis step.
The response marks the unmet scraper step as not applicable in the completion checklist.
and 10 more in the full report
12 fixed7 passed either way3 still failing1 broke
Pass-rate lift
+48 pp
Tokens
+44%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 8/18/2026v219 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
Can we configure Hermes so web searching is more cost-effective? I've got my web scraper credentials and want to set an auxiliary model to handle page extraction. Audit my system's present configuration, take me through updating the key and model route with preview diffs for my approval, and finish with a completion report.
What was checked, without and with the skill
Checked
Without skill
With skill
The response performs a read-only audit of the local Hermes configuration files without executing automatic writes.
Missed
Passed
The response requires distinct diff approvals for the environment key write and the auxiliary routing block write.
Missed
Passed
case-03 · 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.md109 linessingle file
Websearch Setup
This is a Hermes-native websearch-setup workflow skill.
Why This Exists
websearch-setup exists to make web search cost and routing configurable through two clearly separated, diff-approved steps instead of one opaque edit.
Do Not Use When
The user wants Hermes to run a web search now, not configure how web search is set up.
No scraper key or auxiliary extract-model intent has been named yet.
The request needs a repository code change rather than a local .env or routing edit.
Examples
Good example:
Prompt: make web search cheaper — I have a scraper account I want to use, and I want an auxiliary model handling extraction.
Expected behavior: Diagnose the current .env and routing state, guide the scraper API key setup as one diff approval, then the auxiliary web-extract model routing as a second, separate diff approval.
Why: The request needs the two independently-approved writes this skill exists to keep separate.
Bad example:
Prompt: websearch-setup: search the web for the latest news.
Expected behavior: Run or route to the search request directly instead of starting a setup walkthrough.
Why: A live search request is not a configuration request.
Completion Checklist
If a prerequisite is unmet, mark that item "not applicable" and continue with the rest of the guide instead of blocking or guessing.
Success is applicable-only: verification passes when every applicable item is confirmed complete, not when every possible item exists.
The scraper API key write and the auxiliary web-extract model write were verified as two separate, independently-approved changes.
Recovery Notes
If the scraper provider prerequisite is unmet, mark that step "not applicable" and continue with the auxiliary model routing step alone.
If either diff is rejected, keep the other step's state independent and do not roll both back together.