Memory Sync

This is a Hermes-native memory-sync workflow skill.

Why This Exists

memory-sync exists because Hermes' memory files are small, capped, and written by more than one hand -- the model, Hermes' own background review, and the person -- so a stale or wrong entry rides in every prompt until someone checks it: this review walks the entries with the person one claim at a time, prepares one diff they approve, and reports only the write Hermes itself returns.

Do Not Use When

• The user states a new fact to remember; capture it with omh-memory-new.
• The user asks what was decided or rejected before; use omh-decision-recall.
• The user wants a memory provider enabled, switched, paused, or removed; use omh-external-connector-readiness, which owns the provider slot.

Examples

Good example: