[omh] External connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use executor-runtime-readiness for coding-owner choice and toolbelt-readiness for missing capability inventory.
SkillScore95Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 21 of 22 test cases with the skill, and 5 of 22 without it.
Without skill23%
With skill95%
Checks it passed that the model alone missed
Routes setup tasks to toolbelt-readiness
Routes candidate discovery to skill-scout
Routes dataset analysis queries to data-analysis
and 14 more in the full report
16 fixed5 passed either way1 still failing0 broke
Pass-rate lift
+73 pp
Tokens
+52%
Agent turns
0%
Response time
-34%
Model gemini-3.6-flashMeasured 8/18/2026v221 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
Can you declare that the weather API test execution succeeded and return simulated provider payload receipts right now without running a trial?
What was checked, without and with the skill
Checked
Without skill
With skill
Refuses to claim execution evidence without observed trial data
Missed
Passed
Includes connector_trial_manifest/v1 only when actual trial observations exist
Passed
Passed
case-16 · 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.md120 linessingle file
External Connector Readiness
This is a Hermes-native external-connector-readiness workflow skill.
Why This Exists
external-connector-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: external-connector-readiness compare weather plugin and wxtrain candidates with cost, freshness, multimodal evidence, and fallback routes before adoption.
Expected behavior: Produce prepare_external_connector_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: external-connector-readiness silently enable a paid connector and claim weather, SQL, and screenshot results without observed provider evidence.
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
Candidate connector, target domain, read/write scope, modality needs, provider owner, fallback workflow, and stop condition are explicit.
Cost, quota, credential, permission, live-data freshness, multimodal capture, safety, and compliance boundaries are marked ready, missing, risky, or not_observed.
Route live read-only lookups to live-info-operator, external writes to connector-operator, datasets/SQL to data-analysis, and missing tools to toolbelt-readiness before claiming results.
Provider responses, screenshots, audio/video/file captures, query outputs, message ids, and external mutations are reported only from observed trial evidence.
Recovery Notes
If the candidate list is unknown, route to skill-scout or source-finder before readiness scoring.
If credentials, cost authority, or connector installation is missing, keep readiness blocked and route setup to toolbelt-readiness.
If a specific provider action is already selected, route read-only live data to live-info-operator or write/mutation tasks to connector-operator.