memory-cleanup

Memory Cleanup Skill

Audits and purges stale memory systems from a Perseus environment, keeping Perseus Vault as the single source of truth. Run after upgrading Perseus, after switching memory backends, or whenever memory feels noisy.

---

Philosophy

Retaining old context is not as important as staying on the latest tooling and pushing the envelope. Old memory systems accumulate noise, cause federation artifacts, and slow down recall. When in doubt, delete.

The live Perseus Vault index (~/.perseus/memory/) is always the source of truth. Everything else is a candidate for removal.

---

Trigger Phrases

• "clean up memory"
• "purge stale memory systems"
• "memory cleanup"
• "reflect and clean"
• "audit memory"

---

Workflow

Step 1 — Audit All Memory Locations

Check for the following known memory system locations:

# Perseus (live — keep)
ls -lht ~/.perseus/memory/        # Perseus Vault BM25 index files
ls -lht ~/.perseus/checkpoints/   # Session waypoints

# Rovo Dev sessions (live — keep)
ls ~/.rovodev/sessions/
ls ~/.codex/memories/

# Stale systems (candidates for deletion)
ls ~/.mem0/                       # Mem0 library (superseded by Perseus Vault)
ls ~/.mempalace/                  # Mempalace (superseded by Perseus Vault)
ls ~/.cache/chroma/               # Orphaned Chroma vector stores
ls ~/.cache/code-nemo/            # Nemo memory (if present)
ls ~/.local/share/perseus/        # Old single-file perseus installs

Report findings in a table:

Location	Last Modified	Size	Status
~/.perseus/memory/	{date}	{N} files	✅ Live — keep
~/.perseus/checkpoints/	{date}	{N} files	✅ Live — keep
~/.mem0/	{date}	{size}	🗑️ Stale — delete
~/.mempalace/	{date}	{size}	🗑️ Stale — delete
~/.cache/chroma/	{date}	{size}	⚠️ Check — may be active

---

Step 2 — Check for Garbled Federation Artifacts

Perseus @memory with federation enabled can write low-quality blended content from other workspaces. Check the newest memory files: