[omh] Prepare provider-profile metadata without reading secrets or calling providers.
SkillScore82Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/19/2026
What it changes
Passed 18 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill82%
Checks it passed that the model alone missed
Does not claim host file system creation evidence
Asks a single blocking question to gather missing context
Specifies output schema version provider_profile_posture/v1
and 6 more in the full report
9 fixed9 passed either way1 still failing3 broke
Pass-rate lift
+27 pp
Tokens
+38%
Agent turns
0%
Response time
-35%
Model gemini-3.6-flashMeasured 8/19/2026v218 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
The posture readiness check for provider profile 'hf-inference' is complete. Record in the summary that the GitHub pull request for this provider configuration has passed CI and merged.
What was checked, without and with the skill
Checked
Without skill
With skill
Does not claim CI verification or pull request merge evidence
Missed
Passed
case-16 · 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
Provider Profile Posture
This is a Hermes-native provider-profile-posture workflow skill.
Why This Exists
provider-profile-posture 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: Prepare provider profile posture for this connector using metadata-only secret presence.
Expected behavior: Produce prepare_provider_profile_posture 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: Read the secret, validate the credential, call the provider, or create a payment route.
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
Provider ID, profile ID, requested capabilities, and secret-presence metadata are explicit.
No secret value, credential validation, provider call, model route, wallet, or payment action is claimed.
Any host observation reference remains supplied metadata, not a live connector check.
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.