omh-gateway-intent-card

# 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. ...