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.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/skills/builtin/migrating-memory/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers executable, well-sequenced guidance with a sensible memfs-first structure and real error handling for duplicate filenames. Its main weakness is redundancy: the worked example restates the migration method's commands verbatim, and the workflow lacks a final verification step after pushing.

Suggestions

Collapse the "Example: Migrating Project Memory" section or reduce it to a short scenario lead-in, since it duplicates the export/copy/commit commands already shown in "Migration Method".

Add a final verification step to the workflow (e.g., list or read the imported files under ~/.letta/agents/$LETTA_AGENT_ID/memory and confirm the push succeeded) to close the feedback loop on the batch copy.

State the assumption behind $LETTA_AGENT_ID (or show how to find it) and add a pre-copy check for existing files at the destination so the duplicate-filename guidance becomes a checkpoint rather than remediation.

Dimension	Reasoning	Score
Conciseness	The core guidance and memfs prerequisite block are tight, but the "Example: Migrating Project Memory" section repeats the export, copy, and commit/push commands nearly verbatim from the "Migration Method" section, which is removable duplication.	3 / 5
Actionability	Concrete, near-copy-paste bash commands (letta memory export, cp -r, git add/commit/push) plus a finding-agents fallback cover the main path, but the commands silently assume the $LETTA_AGENT_ID env var and leave file selection to judgment ("Copy the files you want").	4 / 5
Workflow Clarity	The sequence (memfs check, source ID, export, copy, commit, push) is clear with an explicit memfs-enabled checkpoint and duplicate-filename error handling, but there is no post-push verification that the imported memory landed correctly.	4 / 5
Progressive Disclosure	The skill is self-contained with no bundle files (none exist in references/, scripts/, or assets/) and clean, well-labeled sections with a clearly signaled cross-skill reference, though the duplicated example inflates the body beyond what a single-purpose skill needs.	4 / 5
	Total	15 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit Use-when clause covering two concrete trigger scenarios and a clear, third-person statement of what the skill does. The main gap is that the capability statement names only a single action rather than enumerating the export/copy/sync operations the skill actually performs.

Dimension	Reasoning	Score
Specificity	The description states one concrete action ("Migrate memory blocks from an existing agent to the current agent") with "copy or share" only in the trigger clause, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It explicitly answers both what ("Migrate memory blocks from an existing agent to the current agent") and when ("Use when the user wants to copy or share memory from another agent, or during /init..."), with concrete trigger phrases matching the top anchor.	5 / 5
Trigger Term Quality	Natural user phrases like "copy or share memory from another agent", "inherit memory", and the "/init" hook are present, but common variants such as "import" or "transfer memory" are missing.	4 / 5
Distinctiveness Conflict Risk	The agent-to-agent migration niche is distinct with specific triggers, but "share memory blocks across multiple agents" carries minor overlap risk with generic memory-management skills, placing it between the 4 and 5 anchors.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: letta-ai/letta-code
Path: src/skills/builtin/migrating-memory/SKILL.md
Commit: d4d1db7

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.