[omh] Hermes agent ops review workflow: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.
SkillScore73Maintained
Automatic
◆Project Management pack
Last verified 8/18/2026
What it changes
Passed 16 of 22 test cases with the skill, and 5 of 22 without it.
Without skill23%
With skill73%
Checks it passed that the model alone missed
Outputs an agent-ops-review/v1 metadata card format.
Labels unobserved remote gateway responses as not_observed.
Labels unverified external runtime telemetry as not_observed.
and 9 more in the full report
11 fixed5 passed either way6 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+25%
Agent turns
0%
Response time
-41%
Model gemini-3.6-flashMeasured 8/18/2026v216 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Provide a status summary after attempting to load the audit plugin. No explicit output or log was recorded confirming whether the plugin reloaded.
What was checked, without and with the skill
Checked
Without skill
With skill
Classifies the unobserved plugin reload as local health diagnostic evidence rather than confirmed runtime state.
Missed
Passed
case-08 · 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.md107 linessingle file
Agent Ops Review
This is a Hermes-native agent-ops-review workflow skill.
Why This Exists
agent-ops-review 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: agent-ops-review show quality, blockers, and throughput for AI-agent work.
Expected behavior: Produce prepare_agent_ops_review 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: agent-ops-review claim Codex finished and CI passed because a handoff exists.
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 local command, managed path, config surface, and state artifact inspected are named.
Blocking issues, warnings, and optional surfaces are separated.
The next repair action is explicit and does not claim a reload or runtime observation.
Recovery Notes
If a managed path or config key is missing, route to setup/update repair instead of editing hidden state.
If a reload or plugin load was not observed, keep the diagnostic result as local health evidence only.