| name | omh-capability-toggle |
| description | ["omh"] |
| Hermes adaptation for turning one OMH capability family on or off so an install can be tailored instead of taken whole. Use when the user says | capability-toggle, capability policy, disable memory, enable memory, disable coding orchestration, disable a capability family, enable a capability family, 메모리 기능 꺼줘. |
| metadata | {"hermes":{"tags":["workflow","oh-my-hermes","operator"],"category":"operator","phase":"configuration","role":"tracker","quality_tier":"evidence-gated"}} |
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.
