Memory Organizer Skill

---

name: memory-organizer

description: Organize, compress, and curate OpenClaw memory without polluting permanent memory. Use when the user wants to compress memory files, clean dated memory notes, reduce startup context, remove redundancy, or keep MEMORY.md focused on must-read long-term facts only. Preserve day-by-day memory files for historical detail, and promote only stable essentials such as user preferences, durable project configuration, and active cross-session todos.

---

# Memory Organizer Skill

Organize memory with a strict two-layer model.

Core Rule

Treat `MEMORY.md` as a small permanent index.

Do not copy every dated memory file into `MEMORY.md`.

Do not turn daily logs into permanent memory.

Keep historical details inside `memory/YYYY-MM-DD.md` files unless a fact is clearly long-lived and should be loaded in every new session.

Memory Model

1. Permanent memory: `MEMORY.md`

Keep only information that is worth reading every session:

This file should stay short, clean, deduplicated, and easy to scan.

2. Daily memory: `memory/YYYY-MM-DD.md`

Keep session-specific and historical detail here:

When compressing or organizing memory, preserve these files instead of moving everything into permanent memory.

Decision Rule: Promote or Keep Local

Before writing anything into `MEMORY.md`, ask:

1. Will this likely matter across many future sessions?

2. Does it need to be loaded immediately at session start?

3. Is it stable enough that it will not create clutter soon?

Only promote the item when the answer is clearly yes.

If the item is useful mainly as history, context, or audit trail, keep it in the dated file.

What to Promote

Promote only concise bullets such as:

What Not to Promote

Do not promote these by default:

Compression Workflow

When the user asks to compress or organize memory:

1. Scan `MEMORY.md` and dated memory files separately.

2. Clean and deduplicate `MEMORY.md` first.

3. Compress dated files in place.

4. Preserve useful historical notes inside their original `memory/YYYY-MM-DD.md` files.

5. Promote only a very small set of durable facts into `MEMORY.md`.

6. If unsure whether something is permanent, leave it in the dated file.

Merge Workflow

If using a merge or promotion action:

Quality Bar

`MEMORY.md` should remain:

If a choice would make `MEMORY.md` longer but not more reusable, keep that content in the dated memory file instead.

Safety