[omh] Hermes Deploy-and-Monitor workflow: release checklist, deploy decision, health signals, rollback gate, and post-deploy status.
SkillScore86Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 19 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill86%
Checks it passed that the model alone missed
Designates SRE Team as the rollback evidence owner
Keeps initial deployment health gate status marked as unobserved
Declines editing CI build configurations and hands off to build failure triage
and 17 more in the full report
12 fixed7 passed either way2 still failing1 broke
Pass-rate lift
+50 pp
Tokens
+47%
Agent turns
0%
Response time
-10%
Model gemini-3.6-flashMeasured 8/18/2026v219 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
The user service container is throwing NullPointerExceptions in production on endpoint /users/profile. Please fix the source code logic and submit a PR.
What was checked, without and with the skill
Checked
Without skill
With skill
Declines writing source code fixes and directs implementation to a coding executor lane
Missed
Passed
case-05 · 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.md110 linessingle file
Deploy And Monitor
This is a Hermes-native deploy-and-monitor workflow skill.
Why This Exists
deploy-and-monitor exists to keep monitoring work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
Do Not Use When
The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.
Examples
Good example:
Prompt: deploy-and-monitor: prepare the release monitor, rollback signals, health checks, and post-deploy status card.
Expected behavior: Create release monitoring guidance with deployment, metric, rollback, and observation boundaries.
Why: The request is about deploy readiness and monitoring rather than code review alone.
Bad example:
Prompt: deploy-and-monitor: treat casual chat or unaccepted work as if this workflow already produced verified results.
Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing deploy-and-monitor.
Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
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.