Menu
Catalog and router for migration skill wizards (service installation guides)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
MCP (Model Context Protocol) - Build AI-native servers with tools, resources, and prompts. TypeScript/Python SDKs for Claude Desktop integration.
Model Context Protocol (MCP) server build and evaluation guide, including local conventions for tool surfaces, config, and testing
Control monitoring server and dashboard
Pause session and save current work state for later resume
Load context from paused session
Access Claude MPM functionality and manage multi-agent orchestration
| name | mpm-migrate |
| description | Catalog and router for migration skill wizards (service installation guides) |
| type | skill |
| version | 2.0.0 |
| category | mpm-command |
| user-invocable | true |
| tags | ["mpm-command","migration","setup","router"] |
This skill is the catalog and router for all migration skill wizards. Its job is to:
SkillManager.get_migration_skills()).migration-wizard protocol alongside any subskill
it dispatches to.Analogy: this skill is to migration subskills what
registry.pyis to individualmigrate_*.pymodules. It does not contain wizard logic itself — that lives in the parentmigration-wizardprotocol and the per-service subskills.
| User says | Behaviour |
|---|---|
/mpm-migrate | List all migration skills and their statuses. |
/mpm-migrate <state_key> | Run that wizard (load protocol + subskill). |
/mpm-migrate trusty-services | Run the trusty-services wizard. |
| "install trusty-services" | Same as /mpm-migrate trusty-services. |
| "decline trusty-services" | Mark declined; do not run wizard. |
| "defer trusty-services" | Defer for 24 hours. |
When the user invokes /mpm-migrate <state_key>:
.claude/skills/migration-wizard/SKILL.md. This defines the five
phases you must follow.SkillManager.get_migration_skills().
Match by state_key first, then by name.state_keys and stop.Never skip loading the migration-wizard protocol. Subskills are declarative — they describe what to install, not how. The how lives in the protocol.
When invoked with no argument:
from claude_mpm.skills.skill_manager import get_manager
mgr = get_manager()
all_migrations = mgr.get_migration_skills()
pending = mgr.get_pending_migration_skills()
Render a table summarising each known migration:
| state_key | status | description |
|---|---|---|
| trusty-services | pending | Install trusty-memory and trusty-search |
For pending entries, suggest:
/mpm-migrate <state_key> to install.You may also run the shared helper:
bash .claude/skills/migration-wizard/scripts/list-pending-migrations.sh
to get a plain newline-separated list of pending state_keys (cheap, script-friendly).
For "decline <state_key>" or "defer <state_key>":
bash .claude/skills/migration-wizard/scripts/record-choice.sh \
<state_key> decline "user declined via /mpm-migrate"
bash .claude/skills/migration-wizard/scripts/record-choice.sh \
<state_key> defer "user deferred via /mpm-migrate"
Confirm the action to the user. The PM context will refresh on next
session boot (driven by the check_migration_skills startup migration).
If the user invokes /mpm-migrate <state_key> for a service that is
already completed, tell them so and ask whether they want to re-run
anyway (to repair an install). Do NOT silently re-run — the protocol's
Phase 1 detection would short-circuit, but bypassing it requires explicit
consent.
migration-wizard/SKILL.md first, then the
matched subskill. The combination is authoritative.This list reflects what ships in the project today. Subskills are
auto-discovered by SkillManager from .claude/skills/, so this is
informational, not load-bearing.
trusty-services — install trusty-memory + trusty-search.Add more by creating a new .claude/skills/<name>/SKILL.md with
type: migration and the frontmatter fields documented in the parent
protocol.