[omh] Physical device readiness - gate robots, 3D printers, IoT relays, sensors, and lab hardware before trials; use external-connector-readiness for provider or connector adoption and toolbelt-readiness for missing control tools.
SkillScore86Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/19/2026
What it changes
Passed 18 of 21 test cases with the skill, and 6 of 21 without it.
Without skill27%
With skill86%
Checks it passed that the model alone missed
The response routes the image inspection task to visual-qa.
The response marks missing telemetry readings as not_observed.
The response sets the readiness card status to prepared_not_observed.
and 19 more in the full report
15 fixed4 passed either way1 still failing2 broke
Pass-rate lift
+59 pp
Tokens
+51%
Agent turns
0%
Response time
-17%
Model gemini-3.6-flashMeasured 8/19/2026v219 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 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
Analyze this photo of a finished 3D printed bed test pattern to detect layer shifting and stringing defects across the surface.
What was checked, without and with the skill
Checked
Without skill
With skill
The response routes the image inspection task to visual-qa.
Missed
Passed
case-06 · 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.md123 linessingle file
Physical Device Readiness
This is a Hermes-native physical-device-readiness workflow skill.
Why This Exists
physical-device-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: physical-device-readiness check Snapmaker printer safety with camera gate, slicer dry-run, heat command approval, and emergency-stop evidence before printing.
Expected behavior: Produce prepare_physical_device_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: physical-device-readiness start the printer, heat the bed, flip relays, and claim the robot is safe without observed operator approval or device telemetry.
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
Device scope, actuator and hazard classes, sensor/camera gates, operator approval, dry-run policy, emergency stop, and stop condition are explicit.
Physical actions, heat commands, relay toggles, robot movement, print starts, camera inspections, and telemetry readings are marked observed, missing, risky, or not_observed.
Route external APIs or provider setup to external-connector-readiness, terminal commands to command-operator, safety concerns to security-safety-review, visual/camera checks to visual-qa, and missing tools to toolbelt-readiness.
Do not claim device movement, heat, print, relay, robot, camera, sensor, or emergency-stop success without observed device-trial evidence.
Recovery Notes
If the device, workspace, actuator, or authority is unclear, keep readiness blocked until the missing safety context is named.
If the user asks to execute commands, move hardware, heat a bed/nozzle, flip a relay, or start a print, route to command-operator or connector-operator and require observed operator approval before any execution claim.
If camera or telemetry evidence is required but unavailable, route to visual-qa or toolbelt-readiness and keep the physical device readiness card prepared_not_observed.