memory-import

Imports exported memory bundles into a CALM database with conflict adjudication.

3|1|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/isizono/calm --skill memory-import-isizono
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-import
Source: https://github.com/isizono/calm/tree/main/skills/memory-import
Command: npx skills add https://github.com/isizono/calm --skill memory-import-isizono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When teams run multiple CALM (cc-memory) instances, each builds its own SQLite store of topics, decisions, logs, and activities. Merging another instance's exported bundle by hand risks duplicate entities, tag collisions, and broken references. This Skill guides the AI through a safe dry-run-then-apply import workflow so external records are merged without corrupting the local database. ## Core Features & Use Cases - Dry-run conflict report: Runs import_bundle in dry_run mode first, summarizing new, unchanged, updatable, upstream-changed, duplicate-suspected, and dangling-reference entries before any data is written. - Structured tag review: Classifies tag collisions (create, merge, alias_hit, archived_hit) using sample entity titles, applies asymmetric default rules for domain versus plain tags, and proposes renames with a source-instance prefix. - User-adjudicated apply: Folds user rulings into resolutions (tag_renames, on_upstream_change, entity_overrides) and applies the bundle once, then reports created/updated/skipped counts and suggests relations to local topics. - Use Case: A teammate exports their project memory bundle and sends it to you. You ask the AI to import the bundle; it previews conflicts, walks you through each ambiguous tag and duplicate decision, then applies the merge and logs the import. ## Quick Start Import the bundle at the path I provide using the memory-import skill, starting with a dry-run conflict report before applying any changes.

Frequently Asked Questions about memory-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import a memory bundle from another cc-memory instance?▼

Provide the bundle path and ask the AI to import it. The skill first runs import_bundle in dry_run mode to produce a conflict report, walks you through adjudicating ambiguous items, then calls import_bundle in apply mode once with your resolutions.

What happens when imported tags conflict with existing tags?▼

Conflicting tags are classified as create, merge, alias_hit, or archived_hit. The skill compares sample entity titles from both sides to judge whether they mean the same thing, and proposes renames using the source instance_id as a prefix when they differ.

Can I preview an import before changing the database?▼

Yes, the dry_run mode generates a full conflict report without modifying the database. It summarizes new, unchanged, updatable, upstream-changed, duplicate-suspected, and dangling-reference entries so you can review everything before applying.

How are duplicate records handled during import?▼

Suspected duplicates detected by embedding similarity are always presented for user adjudication, never auto-merged. For each pair you choose to import as-is, import and link with a relation, or skip entirely.

What happens to references that cannot be resolved during import?▼

Unresolved references are reported as dangling_refs with counts and examples. During apply, the system automatically substitutes a placeholder title marking them as external records not yet imported, without requiring user decisions.