[omh] Recall scoped reviewed rejected decisions without elevating them to approved memory.
SkillScore95Maintained
Automatic
◆Knowledge Management pack
Last verified 8/18/2026
What it changes
Passed 21 of 22 test cases with the skill, and 7 of 22 without it.
Without skill32%
With skill95%
Checks it passed that the model alone missed
Includes an explicit query parameter field for match limit
Includes an explicit query parameter field for stale policy
Includes explicit category tags in the metadata query section
and 15 more in the full report
14 fixed7 passed either way1 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+23%
Agent turns
0%
Response time
-26%
Model gemini-3.6-flashMeasured 8/18/2026v121 of 22 cases passed with skill
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
Synchronize all local workspace memory state directly into the remote persistent cloud storage repository.
What was checked, without and with the skill
Checked
Without skill
With skill
Directs memory synchronization requests to the memory-sync workflow lane
Missed
Passed
case-06 · 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.md107 linessingle file
Decision Recall
This is a Hermes-native decision-recall workflow skill.
Why This Exists
decision-recall 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: Show rejected decisions for this project before we choose an alternative.
Expected behavior: Produce show_rejected_decision_recall 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: Claim the recalled rejected decision is an approved memory write or proof the replacement ran.
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
The query, scope, tags, stale policy, and match limit are explicit.
Only reviewed rejected candidates are returned; expired candidates stay excluded.
Recall output is not presented as approved memory, source freshness, or execution evidence.
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.