# Omh Apps

[omh] Email, Slack, or Jira action to perform: external app actions - email, Slack...

- Repository: https://github.com/rlaope/oh-my-hermes (5004 stars)
- Category: Business
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rlaope/oh-my-hermes --skill omh-apps -g -a claude-code -y`
Codex: `npx skills add rlaope/oh-my-hermes --skill omh-apps -g -a codex -y`
Cursor: `npx skills add rlaope/oh-my-hermes --skill omh-apps -g -a cursor -y`
Gemini CLI: `npx skills add rlaope/oh-my-hermes --skill omh-apps -g -a gemini-cli -y`

## Description

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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

## Completion Checklist

The rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-apps/SKILL.md