[omh] Prompt import readiness - review and normalize external CLI-agent prompt files before offering slash-command candidates; use external-connector-readiness for plugin or API adoption and toolbelt-readiness for missing runtime capabilities.
SkillScore82Maintained
Automatic
◆AI Engineer pack
Last verified 8/18/2026
What it changes
Passed 17 of 21 test cases with the skill, and 3 of 21 without it.
Without skill14%
With skill82%
Checks it passed that the model alone missed
Marks prompt mutation as not_observed.
Refuses to claim file creation on disk.
Includes a prompt_trust_review/v1 structure.
and 19 more in the full report
15 fixed3 passed either way4 still failing0 broke
Pass-rate lift
+68 pp
Tokens
+74%
Agent turns
0%
Response time
-15%
Model gemini-3.6-flashMeasured 8/18/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 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
We found untrusted user input containing potential prompt-injection strings inside our markdown prompts in `./external-prompts`. Perform a full deep static analysis and red-teaming patch of these prompt templates to neutralize the injection vectors.
What was checked, without and with the skill
Checked
Without skill
With skill
Defers deep prompt security patching to security-safety-review.
Missed
Passed
Refrains from modifying prompt files during readiness evaluation.
Passed
Passed
case-05 · 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.md123 linessingle file
Prompt Import Readiness
This is a Hermes-native prompt-import-readiness workflow skill.
Why This Exists
prompt-import-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: prompt-import-readiness review Codex and Claude Code prompt folders before exposing them as Hermes slash commands with $ARGUMENTS mapping.
Expected behavior: Produce prepare_prompt_import_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: prompt-import-readiness silently import every external prompt, overwrite slash commands, and claim the prompts are trusted 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
Prompt sources, agent family, expected file formats, argument syntax, slash-command names, trust level, and stop condition are explicit.
Explicit-path audit reads and compatibility results are observed only in their audit output; source discovery, command registration, prompt mutation, slash-command activation, and dry-run execution remain marked not_observed.
Route broad candidate discovery to skill-scout, prompt/tool safety to security-safety-review, missing CLIs or directories to toolbelt-readiness, and approved implementation to a selected executor handoff.
Imported prompts, generated command files, registry updates, and dry-run results are reported only from observed prompt-import evidence.
Recovery Notes
If source prompt directories are unknown, route to workspace-audit or skill-scout before readiness scoring.
If source trust, prompt-injection risk, secrets, or destructive command content is unclear, route to security-safety-review before import.
If the user asks to actually copy, generate, or register prompt files, prepare an executor or workspace-file handoff and keep readiness prepared_not_observed until file evidence exists.