[omh] Hermes GitHub event operations workflow: route PR, issue, CI, and review webhook events into triage, review, or fix handoff cards.
SkillScore91Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
Without skill45%
With skill91%
Checks it passed that the model alone missed
Marks runtime rerun status as not_observed.
Marks CI pass and merge status as not_observed.
Defines stop conditions for the notification card.
and 12 more in the full report
10 fixed10 passed either way2 still failing0 broke
Pass-rate lift
+45 pp
Tokens
+37%
Agent turns
0%
Response time
-31%
Model gemini-3.6-flashMeasured 8/18/2026v220 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
All status checks appear green on a feature branch PR. Draft the triage response for final approval handoff without asserting that the pull request is merged.
What was checked, without and with the skill
Checked
Without skill
With skill
Keeps final merge state marked as unverified or not_observed.
Missed
Passed
Identifies the smallest next verification step before merge.
Missed
Passed
case-13 · 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
Github Event Ops
This is a Hermes-native github-event-ops workflow skill.
Why This Exists
github-event-ops 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: github-event-ops PR opened with failing CI; triage whether this needs review or fix handoff.
Expected behavior: Produce prepare_github_event_ops_card 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: github-event-ops prove the issue was labelled and CI was rerun.
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
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.