Openclaw-skills memory-organizer

Review and organize memory files (MEMORY.md and memory/*.md). Find duplicates, outdated entries, conflicts, and bloat. Propose promotions, cleanups, and restructuring. Triggers on phrases like "organize memory", "clean up memory", "review memory", "memory audit", "tidy memory", "memory is messy", "consolidate memory files".

install

source · Clone the upstream repo

git clone https://github.com/EasyJoy-Technologies/openclaw-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/EasyJoy-Technologies/openclaw-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/memory-organizer" ~/.claude/skills/easyjoy-technologies-openclaw-skills-memory-organizer && rm -rf "$T"

OpenClaw · Install into ~/.openclaw/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/EasyJoy-Technologies/openclaw-skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/memory-organizer" ~/.openclaw/skills/easyjoy-technologies-openclaw-skills-memory-organizer && rm -rf "$T"

manifest: skills/memory-organizer/SKILL.md

source content

Memory Organizer — Review, Deduplicate, and Restructure

Review all memory layers and produce a structured report of proposed changes. Do NOT apply changes without explicit user approval.

Step 1: Gather All Memory Layers

Read these files (skip any that don't exist):

```
MEMORY.md
```
— primary persistent memory
All files in
```
memory/
```
directory — dated progress notes and topic-specific files
```
AGENTS.md
```
— agent-level configuration and rules (may contain duplicated rules)
```
TOOLS.md
```
— environment reference (may have stale entries)
```
USER.md
```
— user preferences

List each file with its line count and last-modified date.

Step 2: Analyze Each Memory Entry

For each substantive entry in every file, classify it:

Category	Description	Action
Current + Correct location	Still relevant, in the right file	Keep
Current + Wrong location	Still relevant but belongs elsewhere	Propose move
Outdated	No longer true or superseded by newer info	Propose delete
Duplicate	Same info exists in multiple places	Propose consolidate
Conflicting	Contradicts another entry	Flag for resolution
Vague/Trivial	Too generic to be useful ("things are working")	Propose delete
Promotable	Temporary note that proved durable → belongs in MEMORY.md	Propose promote

Location Guidelines

Destination	What Belongs There
MEMORY.md	Durable facts, project conventions, architecture decisions, stable environment details, working rules
memory/YYYY-MM-DD.md	Dated progress notes, temporary findings, unresolved blockers, next-step context
memory/<topic>.md	Topic-specific reference that doesn't fit a single date (e.g., `openclaw-config-safety.md` )
AGENTS.md	Agent workflow rules, risk levels, response style — NOT duplicated facts from MEMORY.md
TOOLS.md	Ports, domains, services, paths — factual environment reference
USER.md	User preferences, timezone, communication style

Step 3: Check for Bloat

For dated memory files (memory/YYYY-MM-DD*.md):

Files older than 30 days: check if all entries have been promoted or are truly obsolete
Files with only 1-2 lines of trivial content: propose deletion
Files that are just conversation transcripts: propose summarize-then-delete

Report total token estimate of all memory files combined.

Step 4: Present the Report

Output a structured report grouped by action:

1. 🔄 Promotions

Entries to move from dated files → MEMORY.md or topic files. Show source, destination, and content.

2. 🗑️ Deletions

Outdated, trivial, or duplicate entries to remove. Show file, line range, and reason.

3. 🔀 Moves

Entries in the wrong file. Show source → destination.

4. ⚠️ Conflicts

Contradictions between files. Show both entries and ask for resolution.

5. 📊 Summary Stats

Total files scanned
Total entries analyzed
Estimated token savings from cleanup
Overall health assessment

Rules

Present ALL proposals before making any changes
Do NOT modify files without explicit user approval
Group related changes so user can approve/reject in batches
When unsure about an entry's relevance, ask rather than propose deletion
Preserve the original structure of MEMORY.md sections