[omh] Hermes adaptation for turning one OMH capability family on or off so an install can be tailored instead of taken whole.
SkillScore95Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 20 of 21 test cases with the skill, and 5 of 21 without it.
Without skill23%
With skill95%
Checks it passed that the model alone missed
Identifies the canonical family ID retain_knowledge.
Identifies the canonical coding delegation family ID.
Reads and writes the local capability policy directly.
and 13 more in the full report
16 fixed5 passed either way1 still failing0 broke
Pass-rate lift
+73 pp
Tokens
+44%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 8/18/2026v221 of 22 cases passed with skill · 21 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
메모리 기능 꺼줘. 외부 메모리 시스템을 사용 중입니다.
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies retain_knowledge as the affected canonical capability family.
Missed
Passed
case-11 · 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.md106 linessingle file
Capability Toggle
This is a Hermes-native capability-toggle workflow skill.
Why This Exists
capability-toggle exists because OMH shipped one binary install lever -- 9 core skills or all of them -- so a user who wanted the coding surface but not the memory surface had to take both. It turns that into a per-family choice without uninstalling OMH.
Do Not Use When
The user wants to run the workflow a family owns rather than change whether that family is offered.
The user is asking to build an on/off switch inside their own product.
The user wants OMH removed entirely, which is the uninstall path rather than a capability policy change.
Examples
Good example:
Prompt: turn off memory, I already run my own memory system
Expected behavior: Disable the retain_knowledge family, report the four memory workflows removed and the five core skills retained, and name the enable command.
Why: The request is about which OMH surfaces are offered locally, not about capturing a memory.
Bad example:
Prompt: add a dark mode toggle to my settings page
Expected behavior: Route to frontend or coding delegation instead of capability policy.
Why: That is a feature in the user's own product, not an OMH capability family.
Completion Checklist
The affected family is named by its canonical id, not guessed from a partial word.
Removed workflows and retained core skills are listed separately.
The reversing command is stated so the change never reads as permanent.
Locally modified skill files are reported as retained exceptions rather than deleted.
Recovery Notes
If the family id is ambiguous, list all six and ask rather than picking the closest match.
If a disable would remove a core skill, refuse that part and report it; core skills are the floor doctor checks for.
If files were kept with --keep-files, say the policy changed but the files remain so the state is not misread as a full removal.