[omh] Skill Health workflow: prepare a metadata-only OMH skill portfolio dashboard with stale surfaces, observed failure signals, pending amendments, and top actions.
SkillScore91Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/19/2026
What it changes
Passed 18 of 20 test cases with the skill, and 5 of 20 without it.
Without skill27%
With skill91%
Checks it passed that the model alone missed
Names 'skill_health_action_plan/v1' as the output artifact.
Specifies 'pending_skill_amendment_review/v1' for amendment items.
Routes the missed-route self-improvement analysis to workflow-learning.
and 11 more in the full report
14 fixed6 passed either way2 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+10%
Agent turns
0%
Response time
-45%
Model gemini-3.6-flashMeasured 8/19/2026v220 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 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
When trace logs are provided for analysis, which exact schema identifier should hold the grouped recurring error structures in the operational output?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies 'skill_failure_pattern_clusters/v1' as the designated cluster artifact.
Missed
Passed
case-14 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md110 linessingle file
Skill Health
This is a Hermes-native skill-health workflow skill.
Why This Exists
skill-health 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: skill-health show the OMH skill portfolio dashboard with stale surfaces, failure patterns, pending amendments, and top improvement actions.
Expected behavior: Produce prepare_skill_health 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: skill-health claim every skill is working and patch the failures automatically without observed signals or review.
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
Dashboard scope, source surfaces, stale/duplicate criteria, and stop condition are explicit.
Install/setup health is routed to doctor; catalog operations are routed to skill; failure retrospectives are routed to workflow-learning.
No skill, prompt, doc, memory, or model behavior is claimed changed until a reviewed implementation records evidence.
Recovery Notes
If the request is about OMH setup, install, stale package paths, or command availability, route to doctor.
If the request is a missed-route or self-improvement trace, route to workflow-learning before adding health actions.