Connector Operator

This is a Hermes-native connector-operator workflow skill.

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; use omh-gateway-intent-card.
• The user is choosing or adopting a new provider, MCP server, or integration rather than acting through one; use omh-external-connector-readiness.
• Launching or quitting a local desktop application; use omh-terminal or the host's computer-use tool.

Examples

Good example: