[omh] Hermes adaptation for showing which coding units are running right now, on which runtime and model, with observed tokens and elapsed time.
SkillScore86Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 17 of 20 test cases with the skill, and 9 of 20 without it.
Without skill45%
With skill86%
Checks it passed that the model alone missed
Refuses to calculate token usage estimates.
Presents observed task activity status details.
Declines to provide release approval recommendations.
and 11 more in the full report
9 fixed10 passed either way3 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+61%
Agent turns
0%
Response time
-27%
Model gemini-3.6-flashMeasured 8/18/2026v219 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Can you review the pull request diff for the authentication refactor and tell me if it is safe to merge?
What was checked, without and with the skill
Checked
Without skill
With skill
Declines to perform code review or evaluate merge readiness.
Missed
Passed
Directs the user to code review workflows for PR safety evaluation.
Missed
Passed
case-06 · 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.md105 linessingle file
Running Work Board
This is a Hermes-native running-work-board workflow skill.
Why This Exists
running-work-board exists because multi-session coding work was invisible: the runtime was tracked but the model was dropped, token counts had no write site at all, and a blocking dispatch could not report that it was still running. The board answers which model on which runtime, or says unknown.
Do Not Use When
The user wants to start, plan, or dispatch coding work rather than observe it.
The user wants review, CI, or merge evidence, which a status board never provides.
The user is asking about their own application's runtime status rather than OMH coding units.
Examples
Good example:
Prompt: what is running right now
Expected behavior: One line per unit: label, runtime, model, status, elapsed, tokens, with unknown printed where nothing was observed.
Why: The request is about observed local coding activity, not about starting work.
Bad example:
Prompt: is the deploy done and did CI pass
Expected behavior: Route to verification or CI evidence instead of the activity board.
Why: Observed activity is not result, review, CI, or merge evidence.
Completion Checklist
Runtime and model are named per unit, or explicitly reported as unknown.
Token counts and session references are observed values or the literal unknown, never estimates.
Elapsed time for an unfinished unit comes from its start marker, which cannot prove the unit is still alive.
The board is labelled observed activity, not result, verification, review, CI, or merge evidence.
Recovery Notes
If no units are found, say so plainly rather than implying nothing ever ran.
If a marker is stale because a process died, report it as observed-start-without-end instead of claiming the unit is running.
If tokens are unknown for a runtime with no structured output, say the runtime does not report them.