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

79%

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

76%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 is highly actionable with copy-paste bash and a clear recommended flow, and is well-structured for its scope. The main gap is the absence of explicit validation/verification before committing and pushing memory changes, which the destructive/batch cap holds at a workflow_clarity of 3.

Suggestions

Add an explicit verification checkpoint before 'git push' (e.g., list the imported files or confirm no unintended overwrites) to lift workflow_clarity above the destructive/batch cap of 3.

Tighten the 'When to Use This Skill' bullets or fold them into the description to remove minor redundancy with the frontmatter.

Make the duplicate-filename handling a concrete step ('before copying, check for existing files and rename/merge') rather than a trailing aside.

Dimension	Reasoning	Score
Conciseness	The body is largely lean — commands and the export→copy→sync flow are stated directly without explaining what memfs or git is — but the duplicate-filename aside and the 'When to Use' bullets add light padding that could be trimmed, matching the score-4 anchor 'Efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	Guidance is fully executable: copy-paste bash commands for export, cp, git add/commit/push with concrete paths and a worked end-to-end example, satisfying the score-5 anchor for copy-paste ready commands covering common cases.	5 / 5
Workflow Clarity	The export→copy→sync sequence is clear, but this involves batch/destructive-style memory writes (overwriting/clobbering memory files via cp -r and git push) with only a vague 'rename the incoming file or merge its contents manually' note and no explicit validate/verify checkpoint before pushing, so the destructive/batch cap holds at 3 per the feedback_loops scoring note.	3 / 5
Progressive Disclosure	Content is well-organized into clearly signaled sections (When to Use, Migration Method, If MemFS Is Disabled, Workflow, Example) with a one-level reference to the finding-agents skill; no bundle files exist, and at this size the structure is appropriate, matching the score-4 anchor 'Good structure; most content is appropriately placed; references mostly clear'.	4 / 5
	Total	16 / 20 Passed

Description

82%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.

The description is well-constructed: it states the purpose plainly and provides explicit, natural 'Use when' triggers tied to concrete scenarios. It is slightly light on enumerating multiple distinct concrete actions, keeping specificity at the midpoint rather than the top.

Suggestions

Optionally expand the action list with a couple more distinct concrete verbs (e.g., 'export, copy, and sync memory blocks') to lift specificity toward comprehensive coverage.

Consider adding the literal phrase 'migrate memory' or 'agent memory' as a keyword synonym so it matches how users most commonly phrase the request.

Dimension	Reasoning	Score
Specificity	Names the domain ('migrate memory blocks') and one concrete action ('copy or share memory') but the action set is thin — it says 'migrate'/'copy'/'share'/'inherit' rather than listing multiple distinct concrete operations, which matches the score-3 anchor 'Names domain and 1-2 concrete actions, but not comprehensive'.	3 / 5
Completeness	Clearly answers 'what' ('Migrate memory blocks from an existing agent to the current agent') and 'when' via an explicit 'Use when...' clause with concrete trigger phrases ('copy or share memory from another agent', 'during /init when setting up a new agent'), matching the score-5 anchor that requires both what and when with concrete triggers.	5 / 5
Trigger Term Quality	Includes natural user-facing phrases ('copy or share memory from another agent', 'inherit memory from an existing one', '/init') covering the main phrasings users would say; a few synonyms or explicit 'migrate memory' keyword variations are missing, placing it just below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	The memory-migration niche is narrow and the triggers ('migrate memory blocks', 'inherit memory', '/init when setting up a new agent') are distinct from other skills, giving it a clear niche with minimal conflict risk per the score-5 anchor.	5 / 5
	Total	17 / 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: 051b47f

Reviewed: 2 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.