/migrating-memory
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.
$ npx -y skills add letta-ai/letta-code --skill migrating-memory --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/migrating-memory
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
migrating-memory.SKILL.mdname: migrating-memory
description: 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.
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_filesystem` block in your system prompt. If it shows a tree structure starting with `/memory/` including a `system/` 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:
1. **Export the source agent's memfs to a temp directory**
letta memory export --agent <source-agent-id> --out /tmp/letta-memory-<source-agent-id>
2. **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/
3. **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".
1. **Get source agent ID from user:** User provides: `agent-abc123`
2. **Export their memfs:**
letta memory export --agent agent-abc123 --out /tmp/letta-memory-agent-abc123
3. **Copy the relevant files into your memfs:**
cp -r /tmp/letta-memory-agent-abc123/system/project ~/.letta/agents/$LETTA_AGENT_ID/memory/system/
4. **Commit and push:**
cd ~/.letta/agents/$LETTA_AGENT_ID/memory
git add system/project
git commit -m "Import project memory"
git push
Read more
name: migrating-memory description: 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.
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_filesystem` block in your system prompt. If it shows a tree structure starting with `/memory/` including a `system/` 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:
1. **Export the source agent's memfs to a temp directory**
letta memory export --agent <source-agent-id> --out /tmp/letta-memory-<source-agent-id>
2. **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/
3. **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".
1. **Get source agent ID from user:** User provides: `agent-abc123`
2. **Export their memfs:**
letta memory export --agent agent-abc123 --out /tmp/letta-memory-agent-abc123
3. **Copy the relevant files into your memfs:**
cp -r /tmp/letta-memory-agent-abc123/system/project ~/.letta/agents/$LETTA_AGENT_ID/memory/system/
4. **Commit and push:**
cd ~/.letta/agents/$LETTA_AGENT_ID/memory git add system/project git commit -m "Import project memory" git push
Letta Code is a stateful agent harness for creating agents that are more like people than tools. Letta Code agents have memory, identity, and a sense of experience over time.
Repo: letta-ai/letta-code
Other skills on letta-code.
- /acquiring-skills
Discover and install skills from Hermes, ClawHub, GitHub, and other registries. Load this skill whenever a user asks for a capability you don't already have — image generation, social media, email, calendar, finance, DevOps, search, browser automation, etc.
Open skill - /context-doctor
Identify and repair degradation in system prompt, external memory, and skills preventing you from following instructions or remembering information as well as you should.
Open skill - /converting-mcps-to-skills
Connect to MCP (Model Context Protocol) servers and create skills for repeated use. Load when a user wants to use an MCP server, connect to external tools via MCP, or when they mention MCP, model context protocol, or specific MCP servers.
Open skill - /creating-mods
Creates and edits trusted local Letta Code mods, including tools, slash commands, local-only model providers, lifecycle/turn events, scoped conversation helpers, panels, and capability-gated behavior. Use when asked to make a mod, add an agent-callable tool, add a slash command,
Open skill - /creating-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Letta Code's capabilities with specialized knowledge, workflows, or tool integrations.
Open skill - /customizing-commands
Creates, edits, and enables Letta Code mod-provided slash commands. Use when the user asks to add a custom /command, slash command, command shortcut, scoped conversation-backed command, or command-driven panel behavior.
Open skill

