[omh] English-canonical Hermes memory-review guidance: inspect USER.md and MEMORY.md claims and prepare a native write diff without invoking, applying, or observing a native write; for a new fact use memory-new, and for a past decision use decision-recall.
SkillScore86Maintained
Automatic
◆Knowledge Management pack
Last verified 8/19/2026
What it changes
Passed 19 of 22 test cases with the skill, and 4 of 22 without it.
Without skill18%
With skill86%
Checks it passed that the model alone missed
Assigns a 90% veracity weight to approved_auto_safe entries.
Enforces a cap of approximately 1,375 characters for USER.md.
Reports the boundary status as not_observed or not_available.
and 17 more in the full report
15 fixed4 passed either way3 still failing0 broke
Pass-rate lift
+68 pp
Tokens
+108%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 8/19/2026v319 of 22 cases passed with skill
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
I want to start a review of our stored context files. What tool call should you issue first to discover our stored memory items, and which parameter action must be provided?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies that omh_memory must be called with the action parameter set to status.
Missed
Passed
Notes that the status call returns metadata and entry counts rather than raw text content.
Missed
Passed
case-07 · 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.md138 linessingle file
Memory Sync
This is a Hermes-native memory-sync workflow skill.
Why This Exists
memory-sync 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: memory-sync inspect stale MEMORY.md claims, prepare a native write diff, and ask which claims to keep, revise, or archive.
Expected behavior: Produce prepare_memory_sync 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: memory-sync claim a prepared native diff changed MEMORY.md or USER.md.
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
Confirm the workflow target, evidence boundary, and stop condition are named.
Report which outputs are prepared, observed, blocked, or missing.
Name the smallest next verification or handoff instead of claiming completion from narration.
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.