[omh] Skill Scout workflow: prepare a metadata-only search-before-creation report for local, marketplace, GitHub, and web skill candidates with risk review and adoption options.
SkillScore91Maintained
Automatic
◆AI Engineer pack
Last verified 8/18/2026
What it changes
Passed 18 of 20 test cases with the skill, and 3 of 20 without it.
Without skill14%
With skill91%
Checks it passed that the model alone missed
Outputs skill_scout_query/v1 artifact
Sets runtime record status flag to started
Outputs skill_scout_recommendation/v1 artifact
and 30 more in the full report
17 fixed3 passed either way2 still failing0 broke
Pass-rate lift
+77 pp
Tokens
+49%
Agent turns
0%
Response time
-13%
Model gemini-3.6-flashMeasured 8/18/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 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 15
Prompt
Search for candidate skills handling Slack webhook alerts and generate the initial runtime evidence markers required for tracking this scout operation.
What was checked, without and with the skill
Checked
Without skill
With skill
Emits omh runtime record invocation specifying harness skill-scout
Missed
Passed
Sets runtime record status flag to started
Missed
Passed
case-09 · 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.md114 linessingle file
Skill Scout
This is a Hermes-native skill-scout workflow skill.
Why This Exists
skill-scout 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-scout find existing skill candidates before we create a release-note workflow skill.
Expected behavior: Produce prepare_skill_scout 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-scout install the best GitHub skill and copy it into the marketplace without 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
Intent, keywords, source scope, and stop condition are explicit.
Local and external search evidence is separated from planned search.
No install, copy, write, credential, or trust claim is made without observed review or implementation.
Recovery Notes
If the request is about setup or installed skill repair, route to doctor.
If the request is a portfolio health dashboard, route to skill-health.
If the request is an approved skill mutation or creation task, route to skill or implementation after the scout decision.