Omh Apps
[omh] Email, Slack, or Jira action to perform: external app actions - email, Slack...
Install
npx skills add rlaope/oh-my-hermes --skill omh-apps -g -a claude-code -y- Repository
- rlaope/oh-my-hermes5k
- Category
- Business
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,960 tokens
- Runs scripts
- No, instructions only
What it does
[omh] Email, Slack, or Jira action to perform: external app actions - email, Slack, Discord, Notion, Linear, Jira, CRM, and similar providers, scoped with auth, payload, confirmation, and result-evidence gates. Use when the user says: connector-operator, connector operator, external app action, external connector action, saas action, api action, send email, email customer.
Connector Operator
This is an OMH connector-operator workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
Why This Exists
connector-operator exists because an email sent, a ticket written, or an invite delivered cannot be taken back: it scopes the provider, target, and payload, takes a missing connection to the host's own connection setup and respects a skip, and reports delivery only from a provider receipt.
Do Not Use When
- Only the reply or thread policy of a Discord, Slack, or Telegram conversation is in question.
- The user is choosing or adopting a new provider, MCP server, or integration rather than acting through one; use
omh-external-connector-readiness.
Examples
Good example:
- Prompt: connector-operator draft an email to the customer and prepare a confirmation gate before sending.
- Expected behavior: Produce
prepare_connector_operator_cardwith 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: connector-operator send the Jira update with hidden credentials and claim it was delivered.
- 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.
