migrating-memory

Name: migrating-memory
Availability: InStock
Author: alvinplayz23

Migrate memory blocks between agents using memfs with legacy fallback.

Updated Mar 1, 2026

Search Tags:#migration #agent #memory #blocks #migrate #memfs

Ready to run

npx skills add https://github.com/AlvinPlayz23/boose --skill migrating-memory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrating-memory
Source: https://github.com/AlvinPlayz23/boose/tree/main/src/skills/builtin/migrating-memory
Command: npx skills add https://github.com/AlvinPlayz23/boose --skill migrating-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating memory blocks between agents to enable memory inheritance and sharing across deployments, reducing setup time and ensuring continuity when replacing or onboarding agents.

Core Features & Use Cases

Memfs-first migration workflow that exports from a source agent and imports into a target agent.
Supports sharing memory blocks across multiple agents and preserving system-attached blocks.
Provides fallback for legacy block commands when memfs is disabled and guides conflict resolution for duplicate labels.

Quick Start

Provide the source agent ID and initiate the memfs-first migration to copy memory blocks into the new agent and synchronize.

Frequently Asked Questions about migrating-memory

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

FAQPage Schema

How do I migrate agent memory blocks to a new deployment?▼

Memfs must be enabled for the primary migration workflow. If memfs is disabled, the Skill provides a fallback using legacy block commands to transfer memory between agents successfully.

How do I resolve duplicate labels when sharing memory across multiple agents?▼

Memory block migration enables memory inheritance and sharing across deployments. It reduces setup time and ensures continuity when replacing old agents or onboarding new agents by preserving system-attached blocks.

Can I use legacy block commands if memfs is disabled?▼

Yes, you can use legacy block commands as a fallback if memfs is disabled. The Skill supports both memfs-based migration for primary transfers and legacy commands as a secondary fallback option.

What's the best way to share memory blocks across multiple agents?▼

The best way to share memory blocks is using the memfs-first migration workflow. It exports blocks from a source agent and imports them into targets, preserving system-attached blocks and coordinating memory across multiple agents.

Why does memory migration require handling duplicate labels?▼

Memory migration requires handling duplicate labels to prevent conflicts when importing blocks into a target agent. Use the --label or --override flags to resolve these overlaps and ensure accurate memory inheritance.