openmemory

name	openmemory
description	Manage persistent memory via OpenMemory MCP. TRIGGER when: user says "remember this", "save to memory", "store this", "recall", "what do you remember about", "check memory", "forget this", "delete memory", "clean up memory", or when agent forms a stable conclusion worth persisting. DO NOT TRIGGER when: user refers to system RAM, process memory, or asks to directly edit memory/MEMORY.md file.

OpenMemory — OpenMemory MCP Operation Playbook

1. Overview

This skill is the operational playbook for OpenMemory (MCP) — a primary persistent memory system; the file-based fallback is a secondary index only (one-line pointers, no full-text copies). Configure project_id based on your workspace (see §4 Step 2).

---

2. HARD-GATE

Any memory operation (save/query/maintain) MUST first go through OpenMemory MCP before considering any file-based fallback. If the auto-memory system attempts a direct write to a local file first, intercept and redirect to this skill's flow.

---

3. Flow Router

Trigger Signal	Route	When
User says "remember this", "save to memory", "store this" — or agent forms a stable conclusion worth persisting	SAVE	Post-task, or at user request
User says "recall", "what do you remember about", "check memory" — or agent needs historical context before answering	QUERY	Pre-task, or when context is insufficient
User says "forget this", "delete memory", "clean up memory" — or agent discovers outdated/wrong/duplicated memory	MAINTAIN	On discovery or user request

---

4. SAVE Flow (5 Steps)

Step 1 — Classify sector