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.