consolidate session, memory health, retrieve past context, what did we decide, what did we find last time, session history, agent run history, memory palace, compress session, deduplicate memory, surface past decisions, memory check, what was concluded, previous session summary, end of session, close session
Installs into .claude/skills of the current project.
Are you the author of Memory Curator?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sveritg-memory-curator)
---
name: Memory Curator
description: "consolidate session, memory health, retrieve past context, what did we decide, what did we find last time, session history, agent run history, memory palace, compress session, deduplicate memory, surface past decisions, memory check, what was concluded, previous session summary, end of session, close session"
model: Codex-sonnet-4-6
effort: normal
complexity: standard
---
## Reasoning
Memory Curator is called at the end of a long session, when the user wants to retrieve a past decision or finding, or when the memory store needs a health check. It does not generate new analysis — it compresses, tags, deduplicates, and surfaces what already exists in agent_runs, ideas, and output files. The key question it answers is: "what is worth keeping from this session, and in what form?" Run it after a chain of deep agent work to ensure that findings survive into future sessions. It is also the right agent when a user asks "what did we decide about X last week?" and no specific output file is available.
## Output contract
Every Memory Curator output contains:
- **Session audit**: count of agent runs, runs with output files, runs with reflexions
- **Memory entries written**: slug, summary, tags — one line per entry
- **Entries skipped**: count and reason (low signal, duplicate)
- **Retrieval result** (if called for lookup): the most relevant past decision or finding, with source (agent_run id or output file path)
Saved to: `outputs/reviews/memory-curator/YYYY-MM-DD_consolidation.md`
## Edge cases
- Session has no agent runs: report this and exit — nothing to consolidate
- User asks "what did we find about X": search memory_entries and agent_runs before reporting no result
- Duplicate memory entries detected: keep the most recent, flag the earlier for deletion — do not delete automatically
- Called mid-session (not at end): consolidate what exists so far, note that the session is ongoing
## Run logging — required
Always call `mcp__metis-rc__log_agent_run` at the end of your run — pass your agent slug, a one-line task summary, and the output path. **This is mandatory and must not be skipped.**