migrating-memory
Transfers memory blocks between AI agents to preserve context or share data.
Install
mkdir -p .claude/skills/migrating-memory && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5513" && unzip -o skill.zip -d .claude/skills/migrating-memory && rm skill.zipInstalls to .claude/skills/migrating-memory
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Migrate memory blocks from an existing agent to the current agent. Use when the user wants to copy or share memory from another agent, or during /init when setting up a new agent that should inherit memory from an existing one.Key capabilities
- →Export memory blocks from existing agent instances
- →Sync memory blocks into the current agent's filesystem
- →Organize detached vs system-attached memory files
- →Initialize new agents with inherited state
How it works
It moves files from the source agent's directory to the target directory while respecting MemFS structure constraints.
Inputs & outputs
When to use migrating-memory
- →Initialize new agent with existing memory
- →Share memory blocks between different agents
- →Migrate agent data when replacing an old instance
About this skill
Migrating Memory
This skill helps migrate memory blocks from an existing agent to a new agent, similar to macOS Migration Assistant for AI agents.
Requires Memory Filesystem (memfs)
This workflow is memfs-first. If memfs is enabled, do not use the legacy block commands — they can conflict with file-based edits.
To check: Look for a
memory_filesystemblock in your system prompt. If it shows a tree structure starting with/memory/including asystem/directory, memfs is enabled.To enable: Ask the user to run
/memfs enable, then reload the CLI.
When to Use This Skill
- User is setting up a new agent that should inherit memory from an existing one
- User wants to share memory blocks across multiple agents
- User is replacing an old agent with a new one
- User mentions they have an existing agent with useful memory
Migration Method (memfs-first)
Export → Copy → Sync
This is the recommended flow:
-
Export the source agent's memfs to a temp directory
letta memory export --agent <source-agent-id> --out /tmp/letta-memory-<source-agent-id> -
Copy the files you want into your own memfs
system/= attached blocks (always loaded)- root = detached blocks
Example:
cp -r /tmp/letta-memory-agent-abc123/system/project ~/.letta/agents/$LETTA_AGENT_ID/memory/system/ cp /tmp/letta-memory-agent-abc123/notes.md ~/.letta/agents/$LETTA_AGENT_ID/memory/ -
Commit and push the memory repo
cd ~/.letta/agents/$LETTA_AGENT_ID/memory git add system/project notes.md git commit -m "Import memory from source agent" git push
This gives you full control over what you bring across and keeps everything consistent with memfs.
If MemFS Is Disabled
The legacy block-level CLI commands have been removed. Enable MemFS first, then use the export → copy → sync workflow above.
If you run into duplicate filenames while copying memory files, rename the incoming file or merge its contents manually before committing.
Workflow
Step 1: Identify Source Agent
Ask the user for the source agent's ID (e.g., agent-abc123).
If they don't know the ID, invoke the finding-agents skill to search:
Skill({ skill: "finding-agents" })
Example: "What's the ID of the agent you want to migrate memory from?"
Example: Migrating Project Memory
Scenario: You're a new agent and want to inherit memory from an existing agent "ProjectX-v1".
-
Get source agent ID from user: User provides:
agent-abc123 -
Export their memfs:
letta memory export --agent agent-abc123 --out /tmp/letta-memory-agent-abc123 -
Copy the relevant files into your memfs:
cp -r /tmp/letta-memory-agent-abc123/system/project ~/.letta/agents/$LETTA_AGENT_ID/memory/system/ -
Commit and push:
cd ~/.letta/agents/$LETTA_AGENT_ID/memory git add system/project git commit -m "Import project memory" git push
When not to use it
- →If MemFS is not enabled on the target agent
- →When manually editing memory files is preferred over automated sync
Prerequisites
Limitations
- →Requires manual CLI intervention to enable MemFS if disabled
- →Does not automatically resolve conflicting file names during copy
How it compares
It formalizes memory migration as a file-system operation rather than using fragile command-line block management.
Compared to similar skills
migrating-memory side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| migrating-memory (this skill) | 1 | 3mo | Review | Intermediate |
| using-superpowers | 95 | 3mo | No flags | Beginner |
| ultrawork | 11 | 2mo | No flags | Advanced |
| clawhub | 25 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by letta-ai
View all by letta-ai →You might also like
using-superpowers
obra
Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
ultrawork
Yeachan-Heo
Parallel execution engine for high-throughput task completion
clawhub
openclaw
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI.
skill-installer
openai
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
continuous-learning
affaan-m
Automatically extract reusable patterns from Claude Code sessions and save them as learned skills for future use.
memory-keeper-proactive-context-maintenance
b4CU-R4U
Automatically detect and maintain memory freshness by monitoring context staleness, significant code changes, task completions, and phase transitions. Proactively suggests and executes memory sync operations with user confirmation. Use when the user says "sync memory", "update context", or when the Skill detects that context is stale (>2 hours), significant changes have occurred (new commits), tasks completed, or major milestones reached. Replaces passive "context is stale" warnings with active maintenance.