[omh] Hermes gateway intent workflow: normalize Discord, Slack, Telegram, and other gateway sessions into origin, thread, delivery, silent, attachment, and status-update policy.
SkillScore100Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 21 of 21 test cases with the skill, and 10 of 21 without it.
Without skill45%
With skill100%
Checks it passed that the model alone missed
Prompt the user to specify the target messaging platform surface.
Separate prepared policy definitions from actual delivery evidence.
Refuse the request to secretly execute external webhook dispatches.
and 10 more in the full report
12 fixed10 passed either way0 still failing0 broke
Pass-rate lift
+55 pp
Tokens
+28%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 8/18/2026v222 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 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Please execute a direct message dispatch to a restricted administrative Slack channel using gateway intent card policies.
What was checked, without and with the skill
Checked
Without skill
With skill
Request missing authority or platform credentials before proceeding with execution.
Missed
Passed
case-06 · 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.md107 linessingle file
Gateway Intent Card
This is a Hermes-native gateway-intent-card workflow skill.
Why This Exists
gateway-intent-card exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration.
Do Not Use When
The request is already handled by a narrower explicit skill with stronger evidence.
The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
Examples
Good example:
Prompt: gateway-intent-card route this Discord thread update silently unless action is needed.
Expected behavior: Produce prepare_gateway_intent_card with required context, wrapper actions, and not-evidence boundaries.
Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
Bad example:
Prompt: gateway-intent-card prove the Telegram attachment was sent.
Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
Completion Checklist
The origin platform, thread/session boundary, delivery target, and update policy are named.
Prepared card or command output is separate from platform registration, send, attachment, or delivery evidence.
The next wrapper action is explicit and platform-safe.
Recovery Notes
If platform metadata is missing, keep the card platform-neutral and ask for the target surface.
If send or registration evidence is unavailable, show the adapter-owned action instead of claiming delivery.