# Omh Content Operator

[omh] Product or company copy to publish or rewrite: scope publish-ready writing...

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

## Install

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

## Description

[omh] Product or company copy to publish or rewrite: scope publish-ready writing, rewriting, summarization, translation, release-note, newsletter, customer-copy, social-copy, README-copy, and email-draft work with audience, tone, style, source, review, and hallucination gates. Use when the user says: content-operator, content operator, content workflow, writing workflow, publish-ready writing, publish ready writing, release notes, release note draft.

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

# Content Operator

This is an OMH `content-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

## Why This Exists

`content-operator` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.

## 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: content-operator draft publish-ready release notes with audience, tone, source scope, review gates, and hallucination checks.
- Expected behavior: Produce `prepare_content_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: content-operator invent missing facts and claim the customer announcement 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 rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-content-operator/SKILL.md