import

Imports memories from an exported Markdown file or MEMORY.md into the current project. Use when migrating from another project, restoring from backup, importing Claude Code native MEMORY.md content, or setting up a new project with existing knowledge.

Quality

81%

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

Quality

Content

75%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 actionable, well-sequenced, and efficiently written with concrete commands and error handling. It would reach top marks by offloading the competing-tools reference table to a separate file and adding an explicit post-import verification checkpoint.

Suggestions

Move the competing-tools table and T1-T4 details into a references file (e.g. COMPETING_TOOLS.md) and link to it, keeping SKILL.md as an overview.

Add an explicit validation checkpoint after Step 4 (e.g., compare imported count against parsed-record count) to strengthen the batch-import feedback loop.

Resolve the '<PLUGIN_ROOT>' placeholder into concrete platform-specific snippets or reference the resolver script so commands are directly copy-pasteable.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes competence, but the competing-tools section and MEMORY.md section add inline tables and reporting templates that could be tightened or offloaded to references.	4 / 5
Actionability	Provides executable bash commands, concrete add_memory parameter lists, and copy-paste report strings; minor gaps like un-expanded '<PLUGIN_ROOT>' placeholders keep it just below 5.	4 / 5
Workflow Clarity	Sequenced steps with explicit error branches and stop conditions ('If the script fails... print and stop'); a batch import without an explicit verify-record-count checkpoint holds it at 4 rather than 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Execution, --tools, MEMORY.md, Error Handling) with one-level-deep script references; the competing-tools detail inlined in SKILL.md rather than a separate reference is the minor gap.	4 / 5
	Total	16 / 20 Passed

Description

87%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 specific, trigger-rich, and explicitly covers both what the skill does and when to use it, with low conflict risk. Minor additional action verbs or synonyms would push specificity and trigger coverage to a perfect 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Imports memories from an exported Markdown file or MEMORY.md', 'migrating from another project, restoring from backup') but stops short of a comprehensive enumeration of import operations, so it sits just below a 5.	4 / 5
Completeness	Clearly answers 'what' ('Imports memories from an exported Markdown file or MEMORY.md') and 'when' ('Use when migrating... restoring... importing... or setting up a new project') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'migrating from another project', 'restoring from backup', and 'MEMORY.md' are present, though a few common synonyms (e.g. 'merge', 'load memories') are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (mem0 import from exports or native MEMORY.md) with distinct triggers unlikely to collide with other skills.	5 / 5
	Total	18 / 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: mem0ai/mem0
Path: integrations/mem0-plugin/skills/import/SKILL.md
Commit: dae67f7

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