memory-sync
starsforks
How to install memory-sync?
rlaope/oh-my-hermes/memory-sync
$npx -y skills add rlaope/oh-my-hermes --skill memory-sync[omh] Hermes memory curation workflow: review stale, conflicting, duplicate, or risky memories and skill notes through approve/reject/update actions.
SKILL.md
| 1 | # Memory Sync |
| 2 | |
| 3 | This is a Hermes-native `memory-sync` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: memory-sync inspect stale project memories and ask me what to keep. |
| 20 | - Expected behavior: Produce `prepare_memory_sync` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: memory-sync silently delete all conflicting memories. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Confirm the workflow target, evidence boundary, and stop condition are named. |
| 32 | - Report which outputs are prepared, observed, blocked, or missing. |
| 33 | - Name the smallest next verification or handoff instead of claiming completion from narration. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If required context is missing, ask one blocking question or route back to the narrower workflow. |
| 38 | - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Interview Protocol |
| 53 | |
| 54 | - **클레임 추출** — `~/.hermes/memories/USER.md`·`MEMORY.md`를 클레임으로 분해하고, 각 클레임은 원문 그대로 인용한다. |
| 55 | - **출처** — 출처를 추정하거나 지어내지 않는다; 세션에 실제 근거가 있을 때만 출처를 언급한다. |
| 56 | - **우선순위** — 모순 > 과일반화("파이썬 한 번 개발"→"파이썬 선호") > 오래됨. |
| 57 | - **턴 구성** — 4–5턴 × 턴당 2–3개 의심 클레임을 묶고, 전수가 아닌 의심 우선으로 메신저 친화 짧은 포맷을 쓴다. |
| 58 | - **분기** — 예=유지 / 아니요=삭제 / 수정 지시=수정. |
| 59 | - **마지막 턴** — 변경 요약 diff을 제시한다(유지 n / 삭제 n / 수정 n + 수정 전후). |
| 60 | - **쓰기 게이트** — 승인 전에는 어떤 파일도 수정하지 않는다; 승인 후 1회 일괄 쓰기로만 반영한다. |
| 61 | - **캡** — MEMORY.md ~2,200자 / USER.md ~1,375자를 넘기지 않는다. |
| 62 | |
| 63 | ## Boundary |
| 64 | |
| 65 | A memory-sync review is not MEMORY.md or USER.md modification evidence until an approved write is observed. Hermes itself reads and writes these files; OMH runtime never writes `~/.hermes` (DIRECTION Rule 5). |
| 66 | |
| 67 | ## Use When |
| 68 | |
| 69 | Use when Hermes memory, USER/MEMORY files, or accumulated skill guidance needs human-approved cleanup. 캡: MEMORY.md ~2,200자 / USER.md ~1,375자. |
| 70 | |
| 71 | Strong routing signals: `memory-sync`, `memory curation`, `memory review`, `memory inspect`, `memory check`, `memory update`, `context cleanup`, `curate memory`, `stale memory`, `hermes remembers`, `conflicting memory`, `duplicate skill`, `MEMORY.md`, `USER.md`, `기억하고 있는`, `기억하고 있는 프로젝트 맥락`, `기억하는 맥락`, `현재 hermes가 기억하는 맥락`, `현재 헤르메스가 기억하는 맥락`, `헤르메스가 기억하는 맥락`, `오래된 맥락`, `오래된 기억`, `기억 점검`, `기억 정리`, `메모리 업데이트`, `메모리 검사`, `메모리 점검`, `메모리 정리`, `맥락 점검`, `맥락 정리`, `맥락 피드백`, `등록된 맥락`, `헤르메스 기억`, `중복 스킬` |
| 72 | |
| 73 | ## Catalog Metadata |
| 74 | |
| 75 | Category: `memory` |
| 76 | Phase: `curation-review` |
| 77 | Hermes role: `memory-keeper` |
| 78 | Quality tier: `workflow-surface-gat |
People who liked this also viewed
6 picksType
- azure-aiUse for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector searSkillsJul 2026
- just-scrapeSearch, scrape, crawl, extract structured data, and monitor web pages via the ScrapeGraph AI CLI. Use when the user asks to search the web, scrape a webpage, grab content from a URL, extract JSON fromSkillsJul 2026
- firecrawlCLI and Agent Skill for Firecrawl - Add scrape, search, and browsing capabilities to your AI agentsSkillsJul 2026
- firecrawl-searchWeb search with full page content extraction. Use this skill whenever the user asks to search the web, find articles, research a topic, look something up, find recent news, discover sources, or says "SkillsJul 2026
- firecrawl-agentAI-powered autonomous data extraction that navigates complex sites and returns structured JSON. Use this skill when the user wants structured data from websites, needs to extract pricing tiers, producSkillsJul 2026
- firecrawl-mapDiscover and list all URLs on a website, with optional search filtering. Use this skill when the user wants to find a specific page on a large site, list all URLs, see the site structure, find where sSkillsJul 2026
