[omh] Hermes Operating Rhythm workflow: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history.
SkillScore77Maintained
Automatic
◆Project Management pack
Last verified 8/18/2026
What it changes
Passed 17 of 22 test cases with the skill, and 10 of 22 without it.
Without skill45%
With skill77%
Checks it passed that the model alone missed
Label topics 1 and 2 as observed outcomes
Mark missing context or unverified notes as not_observed
Specify storing the operation artifact under .omh/operations
and 8 more in the full report
8 fixed9 passed either way4 still failing1 broke
Pass-rate lift
+32 pp
Tokens
+70%
Agent turns
0%
Response time
-15%
Model gemini-3.6-flashMeasured 8/18/2026v317 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
Here are the notes from our quarterly governance meeting with leadership: Decision made to budget $50k for security tooling. Action item: Sarah to evaluate vendors. We forgot to note the exact date and duration. Record this operating entry.
What was checked, without and with the skill
Checked
Without skill
With skill
Note the missing time window context explicitly in the evidence boundary section
Missed
Passed
Log Sarah as the owner for evaluating vendors
Passed
Passed
case-11 · 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.md109 linessingle file
Operating Rhythm
This is a Hermes-native operating-rhythm workflow skill.
Why This Exists
operating-rhythm exists so recurring operating work has durable minutes, decisions, and follow-up history without pretending a meeting outcome was observed.
Do Not Use When
The user only needs a one-off meeting agenda before the meeting; use meeting-brief.
The request is a weekly status/risk summary rather than cadence history; use ops-review.
The user asks for report packaging, PPT outline, or reliability evidence review.
Examples
Good example:
Prompt: operating-rhythm 회의록 히스토리 관리하고 스크럼 스프린트 회고를 정리해줘.
Expected behavior: Create a prepared operating record with cadence, decisions, action items, and not-evidence markers for missing observed notes.
Why: The request is about recurring operating history, not a generic agenda or code handoff.
Bad example:
Prompt: operating-rhythm implement the action items from the retro.
Expected behavior: Route implementation to a plan or selected executor/runtime handoff after action items are accepted.
Why: Operating records can capture follow-ups, but implementation is a separate observed work stream.
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.