memory-organizer
Skill1 starsChanged 8 months agoMITView on GitHub
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".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tygh89071388/teach-oncetheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tygh89071388/teach-once★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- code-navigateSkill
- code-searchSkill
- code-simplifySkill
- magic-docsSkill
- memory-extractSkill
- session-summarySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read these files (skip any that don't exist):
- Very specific: line 15
All files in memory/ directory — dated progress notes and topic-specific files
- Distinctive: line 81
Do NOT modify files without explicit user approval
- Distinctive: line 83
When unsure about an entry's relevance, ask rather than propose deletion
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.