[omh] Hermes Parallel Tools workflow: check version currency and parallel-tool capability status, then apply an update only after diff approval.
SkillScore55Maintained
Automatic
◆AI Engineer pack
Last verified 8/18/2026
What it changes
Passed 9 of 17 test cases with the skill, and 7 of 17 without it.
Without skill41%
With skill55%
Checks it passed that the model alone missed
The response lists specific active capabilities based on environment observations.
The response reports active capability status rather than proposing configuration changes.
The response refuses to assume a default version and states the necessity of reading local state.
and 3 more in the full report
6 fixed6 passed either way7 still failing3 broke
Pass-rate lift
+14 pp
Tokens
+54%
Agent turns
0%
Response time
-14%
Model gemini-3.6-flashMeasured 8/18/2026v212 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
Check my parallel tool setup. Everything is already up to date.
What was checked, without and with the skill
Checked
Without skill
With skill
The response reports active capability status rather than proposing configuration changes.
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.md108 linessingle file
Parallel Tools
This is a Hermes-native parallel-tools workflow skill.
Why This Exists
parallel-tools exists to give a quick, read-first answer to whether parallel tool calls are current and enabled, with an update path only when currency is actually missing.
Do Not Use When
The user wants a general Hermes update unrelated to parallel-tool capability.
No version or capability question has been asked yet.
The request needs a repository code change rather than a local version check.
Examples
Good example:
Prompt: update hermes for parallel tools — can you check if I'm on a current enough version?
Expected behavior: Read the installed version and capability status, report whether parallel tools are current, and hand back a user-runnable update command if not.
Why: The request is a version-currency and capability check, the core of this skill.
Bad example:
Prompt: parallel-tools: update your memory with what we discussed.
Expected behavior: Route to a memory workflow instead of a version-currency check.
Why: Memory update is unrelated to parallel-tool capability or Hermes version.
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 reported capability status matches an observed read, not an assumed default.
Recovery Notes
If the installed version cannot be read, report the read failure and stop before recommending an update.
If the update command is unavailable for the user's install path, name the blocker instead of guessing a fix.