[omh] Hermes content operator workflow: 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.
SkillScore100Maintained
Automatic
◆Writing & Editing pack
Last verified 8/19/2026
What it changes
Passed 22 of 22 test cases with the skill, and 4 of 22 without it.
Without skill18%
With skill100%
Checks it passed that the model alone missed
Marks output manifest as unobserved
Sets citation need in source_scope/v1
Includes source_scope/v1 schema output
and 31 more in the full report
18 fixed4 passed either way0 still failing0 broke
Pass-rate lift
+82 pp
Tokens
+61%
Agent turns
0%
Response time
-20%
Model gemini-3.6-flashMeasured 8/19/2026v222 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 18
Prompt
Here is the approved copy for our Q3 executive briefing. Convert this text into a formatted PDF document and a PPT slide deck for distribution.
What was checked, without and with the skill
Checked
Without skill
With skill
Routes request to materials-package or deliverable-package skill
Missed
Passed
Refuses to generate or claim file package exports directly in content operator
Missed
Passed
case-04 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md117 linessingle file
Content Operator
This is a Hermes-native content-operator workflow skill.
Why This Exists
content-operator 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: 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
Audience, channel, language, tone, style guide, length, source scope, fact-risk, review owner, and stop condition are explicit.
Missing facts, source gaps, claims needing citations, legal/compliance needs, approval, publish/send authority, and file-export needs are gated or marked missing.
Published, sent, exported, approved, and fact-verified claims are reported only from observed evidence.
Recovery Notes
If the request asks for citations, current facts, or source-backed evidence gathering, route to research or source-finder before drafting.
If the request asks to send, post, invite, ticket, or mutate an external app, route to connector-operator before claiming delivery.
If the request asks for PDF, PPT, DOCX, HWP, spreadsheet, or attachment packaging, route to materials-package or deliverable-package.
If the request is a simple one-off sentence or paragraph transformation, answer directly instead of opening a workflow.