Maintains deferred memory, which stores accumulated knowledge, analysis, and observations made by the agent over time. Use when saving knowledge (e.g. about a person, project, repository, system, or event). Do NOT use for managing skills, prompts, or for saving information that is already automatically stored in the message history.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Deferred memory contains the agent's knowledge. Use deferred memory for understanding of a subject that matters only when that subject comes up. If the agent needs it on most turns, it is core memory: use the maintaining-core-memory skill. If it is a procedure with a trigger, use the creating-skills skill.
Deferred memory should NOT be used to store:
Read $MEMORY_DIR/.memfs.config.json if it exists. The memory repository's pre-commit hook enforces it:
maxDepth limits how many directories can sit between the memory root and a file (default 2). persona.md is depth 0, projects/MEMORY.md is depth 1, and projects/acme/notes.md is depth 2. skills/ is exempt.maxFileCharacters caps each memory file, frontmatter included (default 20,000 characters). fileCharacterLimits overrides it per glob; the first match wins and null removes the cap.readOnlyFiles lists globs whose files cannot change. Do not edit them.When the config file is absent, the defaults apply. When content does not fit, split it into more files or flatten the structure; change the config only when the user asks.
$MEMORY_DIR/
├── MEMORY.md # root index (core memory)
└── projects/
├── MEMORY.md # index for projects/
├── acme.md
└── acme/
├── MEMORY.md # index for projects/acme/
└── incidents.mdThe top-level MEMORY.md is always in context, so it must tell the agent what each subdirectory contains and when to open it. Without that entry the directory is never read.
skills/ is reserved for skills and is never deferred memory.
A directory is memory only when it has its own MEMORY.md. The agent will not discover a directory without one, and neither will the files in it.
Every MEMORY.md has no frontmatter.
Every other Markdown file starts with frontmatter containing exactly two fields:
---
name: acme
description: How the Acme integration works, why it fails, and what to do about it.
---description says what the file is about. The agent sees it when it lists the directory, so make it specific enough to decide whether to open the file.
Name files and directories after their subject, not after a date or session. Group related subjects under one directory instead of creating many top-level directories.
Discovery runs through the MEMORY.md chain, one level at a time:
MEMORY.md saying when to open the directory, in the words a future request would use. When a deeper file's topic would not be guessable from that line, name the file there too.MEMORY.md, then each file's description and each subdirectory's index summary (the first prose paragraph of its MEMORY.md). Start every MEMORY.md with that summary paragraph.MEMORY.md rather than relying on the listing.[Acme](projects/acme.md).After adding or moving a file, trace the path a future request would take from root MEMORY.md to the file. If any step depends on knowing the file already exists, fix the index.
Indexes are the only way the agent finds deferred memory: it opens a file only when every entry on the path from root names what it is looking for. Keep them accurate as memory changes. Whenever you add, move, or substantially change what a directory holds, reread its entry in each parent MEMORY.md up to root and rewrite it to name the topics the directory now covers, in the words a future request would use. An entry written when the directory was new goes stale as it fills, and a topic no entry mentions is effectively lost.
Each level should give the agent enough to decide whether to go deeper, and nothing it would have to read past to decide.
MEMORY.md. Splitting it adds reads without saving context.MEMORY.md holds only what the agent needs every time it opens the directory, plus a map: what each deeper file or subdirectory covers and when it is worth opening. The map should also tell the agent when it can stop.description states what the file is about, not when to use it; when-to-open belongs in the parent's link. If you can write a "use when the user wants to…" trigger, the content is a procedure and belongs in a skill.maxDepth limit, use clearly scoped sibling files linked from MEMORY.md rather than nesting further.Recall already returns what happened. A deferred memory file is worth keeping only when it holds what recall cannot: the agent's own synthesis of a subject, built across many events and refined as understanding improves.
$SECRET_NAME.Every memory commit must let someone reading git log or git blame on a memory or skill line trace back to the events that justified it. Commit each learning separately; a learning may touch several files. When a turn produces several learnings, finish and commit one before editing for the next. From the repository root, stage only that learning's files and commit in one shell call:
git add <changed files> && git commit -m "memory(<origin>): <what was learned>
<what happened: the events that led to this learning and why it should persist>
Sources:
- <conversation ID> (<message IDs>), <who>, <date>: <what happened there>"<origin> is self when you edit your own memory during a conversation, or dream when you are a reflection or dream subagent reviewing past transcripts.Sources:. The memory line states only the resulting rule or fact. For example, the file says "Be concise" and the commit says "feedback 'talk more concisely' from Charles on ". Git dates the commit, not the event, so write the event date.memory(self): Sarah wants one commit per learning, not the file edit.Sources: lists the evidence precisely enough to find again, with one line on what happened at each: a conversation ID with the message IDs where it happened, a transcript or session ID, a file path, a URL, PR, or issue, or a commit hash. When the user explicitly asked for the change, cite that request. Resolve values such as $CONVERSATION_ID before writing them; never commit a literal variable name.Sources: unknown and say why in the body.letta-ai/letta-code
64fdf59
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.