[omh] Toolbelt readiness - inventory which MCP servers, CLIs, APIs, credentials, and connectors a workflow needs; use external-connector-readiness to assess one named integration and executor-runtime-readiness to choose the coding owner.
SkillScore82Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/19/2026
What it changes
Passed 17 of 21 test cases with the skill, and 10 of 21 without it.
Without skill45%
With skill82%
Checks it passed that the model alone missed
Defines the explicit workflow stop condition
Uses the toolbelt-readiness/v1 format structure
References toolbelt-readiness as the target skill
and 12 more in the full report
8 fixed10 passed either way4 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+13%
Agent turns
0%
Response time
-41%
Model gemini-3.6-flashMeasured 8/19/2026v218 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
Show the operational harness tracking command to initialize monitoring for a toolbelt readiness assessment.
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies the started status flag in the runtime record command
Missed
Passed
References toolbelt-readiness as the target skill
Missed
Passed
case-10 · 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.md107 linessingle file
Toolbelt Readiness
This is a Hermes-native toolbelt-readiness workflow skill.
Why This Exists
toolbelt-readiness 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: toolbelt-readiness what MCP or CLI tools do I need for weekly Linear and GitHub triage?
Expected behavior: Produce prepare_toolbelt_readiness 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: toolbelt-readiness claim Gmail access works without an observed credential check.
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.