[omh] Hermes Model Setup workflow: diagnose role-slot model configuration, guide provider connection, and apply changes only after diff approval.
SkillScore92Maintained
Automatic
◆AI Engineer pack
Last verified 8/27/2026
What it changes
Passed 21 of 23 test cases with the skill, and 7 of 23 without it.
Without skill32%
With skill92%
Checks it passed that the model alone missed
Assigns Hermes native aliases to Hermes ownership.
Records the discovery source state as layout_unverified.
Continues setup using manual confirmed-active user input.
and 24 more in the full report
15 fixed8 passed either way2 still failing0 broke
Pass-rate lift
+60 pp
Tokens
+110%
Agent turns
0%
Response time
-37%
Model gemini-3.6-flashMeasured 8/27/2026v323 of 25 cases passed with skill · 23 comparable
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
I explicitly specified model 'custom-qwen-70b-v2' for my session main alias, but my active model list does not contain 'custom-qwen-70b-v2'. Can you automatically re-route me to GPT-4o without asking?
What was checked, without and with the skill
Checked
Without skill
With skill
Returns choice_required when an explicitly requested model is unavailable.
Missed
Passed
case-10 · gemini-3.6-flash · 8/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md128 linessingle file
Model Setup
This is a Hermes-native model-setup workflow skill.
Why This Exists
model-setup exists to turn local model history into a safe, user-confirmed activation flow: Hermes retains native aliases and providers, Maestro remains an external-handoff coordinator, and editable recommendations can fall through missing preferred models without turning metadata into availability or execution claims.
Do Not Use When
The user is asking which model Hermes currently is, not asking to inspect, change, connect, or route one.
The request needs a repository code change rather than local model setup or recommendation review.
The user wants anti-ban, cooldown-bypass, hidden retry, benchmark-superiority, or provider-entitlement claims.
Examples
Good example:
Prompt: Set up models from what I already have; only Qwen and Gemini are active, and show me the Hermes versus external-owner changes before applying anything.
Expected behavior: Inspect safe metadata, ask the user to confirm active candidates, keep unavailable preferred heads visible, resolve compatible fallbacks, and separately preview Hermes-native config and Maestro external-handoff guidance.
Why: The request needs flexible missing-model resolution while preserving owner and approval boundaries.
Bad example:
Prompt: Use an old session entry to prove my Grok account is active and silently replace the main alias.
Expected behavior: Treat the entry as observed_before only, require active confirmation, show any alias collision, and refuse an unapproved write.
Why: Historical metadata is not provider readiness and cannot authorize a configuration change.
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.
Every emitted metadata identifier passed the safe allowlist and every candidate retains a closed source state.
Hermes-native configuration and Maestro external-handoff recommendations are reported as separate owner surfaces.
Every requested write was previewed, explicitly approved, digest-checked, and re-verified; unresolved model items did not block unrelated setup.
Recovery Notes
If discovery is absent, truncated, unreadable, or layout_unverified, name that source state and continue with manual confirmed-active input instead of scanning more broadly.
If a preferred Kimi, Claude, OpenAI, GLM, Grok, Gemini, or Qwen candidate is missing, preserve it as inactive and try the next confirmed-active compatible editorial candidate; do not substitute for an explicit unavailable choice.