[omh] Hermes Scheduled Ops Blueprint workflow: design recurring Hermes operations with schedule, delivery, silence policy, context chain, and prepared-vs-observed status.
SkillScore77Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 16 of 21 test cases with the skill, and 3 of 21 without it.
Without skill14%
With skill77%
Checks it passed that the model alone missed
Specifies that the skill is gated by operational blueprint standards
Treats wrapper memory or context summaries as advisory local context
Notes background watchdog candidacy without claiming active execution
and 23 more in the full report
14 fixed3 passed either way5 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+33%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 8/18/2026v317 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
What are the designated catalog metadata parameters for quality tier, reasoning demand, and primary category for the automation-blueprint workflow skill?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies that the skill is gated by operational blueprint standards
Missed
Passed
Categorizes the skill under operational workflows with low reasoning demand
Missed
Passed
case-19 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md115 linessingle file
Automation Blueprint
This is a Hermes-native automation-blueprint workflow skill.
Why This Exists
automation-blueprint exists so Hermes can make recurring operational work feel native and scheduled without OMH becoming a hidden cron runner, transport bot, source retriever, or executor.
Do Not Use When
The user needs a one-off report or deck; use report-package or materials-package.
The user asks to review incident metrics once; use reliability-review.
The user needs actual code changes; prepare a selected executor/runtime handoff after the blueprint or plan is accepted.
Examples
Good example:
Prompt: automation-blueprint every weekday run an uptime check and send a Slack digest only if status changes.
Expected behavior: Prepare hermes_ops_blueprint/v1 with schedule intent, Slack delivery policy, silence rule, research/report skills, missing evidence, and next confirmation.
Why: The request is recurring, delivery-shaped, and must stay prepared until host automation and gateway delivery are observed.
Bad example:
Prompt: automation-blueprint prove the Slack digest was delivered this morning.
Expected behavior: Ask for observed Hermes/gateway delivery evidence or report the delivery as not_observed instead of claiming it happened.
Why: A blueprint can prepare the scheduled operation, but it cannot prove runtime execution or delivery.
Completion Checklist
Confirm the workflow target, evidence boundary, and stop condition are named.
Report which outputs are prepared, observed, blocked, or missing.
Name the smallest next verification or handoff instead of claiming completion from narration.
Recovery Notes
If required context is missing, ask one blocking question or route back to the narrower workflow.
If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.