Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
bobmatnyc avatar

Mpm Migrate

  • 1 installs
  • 145 repo stars
  • Updated July 27, 2026
  • bobmatnyc/claude-mpm

mpm-migrate is a Claude Code skill that acts as a catalog and router for claude-mpm migration wizards, listing subskills and loading the matched one with its protocol.

About

mpm-migrate is a catalog and router for the claude-mpm migration skill wizards. It lists known migration subskills and their status, then loads the matched subskill together with the shared migration-wizard protocol when the user picks one to run. A developer uses it to discover and dispatch service-installation wizards inside a claude-mpm project. It holds no wizard logic itself; the procedure lives in the parent protocol.

  • Lists migration subskills with pending/deferred/declined/completed status
  • Routes the user to the right migration wizard and loads the shared protocol
  • Records decline/defer choices and refuses to silently re-run completed wizards

Mpm Migrate by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #1,980 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
At a glance

mpm-migrate capabilities & compatibility

Capabilities
skill dispatch · migration status
From the docs

What mpm-migrate says it does

This skill is the **catalog and router** for all migration skill wizards.
SKILL.md
**Always** load the `migration-wizard` protocol alongside any subskill it dispatches to.
SKILL.md
Do NOT silently re-run — the protocol's Phase 1 detection would short-circuit, but bypassing it requires explicit consent.
SKILL.md
npx skills add https://github.com/bobmatnyc/claude-mpm --skill mpm-migrate

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars145
Last updatedJuly 27, 2026
Repositorybobmatnyc/claude-mpm

What it does

Discover, dispatch, or decline claude-mpm migration wizards from a single router command.

Who is it for?

developers using claude-mpm who need to manage service-migration wizards from one entry point

When should I use this skill?

the user runs /mpm-migrate or asks to install, list, decline, or defer a migration wizard

By the numbers

  • five-phase migration-wizard protocol
  • 24-hour defer window

Files

SKILL.mdMarkdownGitHub ↗

/mpm-migrate — Migration Skill Catalog & Router

This skill is the catalog and router for all migration skill wizards. Its job is to:

1. List known migration subskills (via SkillManager.get_migration_skills()). 2. Surface their current status (pending / deferred / declined / completed). 3. Load the appropriate subskill when the user picks one to run. 4. Always load the migration-wizard protocol alongside any subskill it dispatches to.

Analogy: this skill is to migration subskills what registry.py is to
individual migrate_*.py modules. It does not contain wizard logic
itself — that lives in the parent migration-wizard protocol and the
per-service subskills.

Invocation Forms

User saysBehaviour
/mpm-migrateList all migration skills and their statuses.
/mpm-migrate <state_key>Run that wizard (load protocol + subskill).
/mpm-migrate trusty-servicesRun 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.

Behaviour: Run a Wizard

When the user invokes /mpm-migrate <state_key>:

1. Always load the parent protocol first: .claude/skills/migration-wizard/SKILL.md. This defines the five phases you must follow. 2. Resolve the named subskill via SkillManager.get_migration_skills(). Match by state_key first, then by name. 3. If no skill matches, list available state_keys and stop. 4. Read the subskill's frontmatter (the declarative data) AND its body (motivation, gotchas, post-install notes). 5. Execute the five-phase protocol with that data.

Never skip loading the migration-wizard protocol. Subskills are
declarative — they describe what to install, not how. The how lives in
the protocol.

Behaviour: List Pending Migrations

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_keystatusdescription
trusty-servicespendingInstall trusty-memory and trusty-search

For pending entries, suggest:

  • /mpm-migrate <state_key> to install.
  • "decline <state_key>" to permanently dismiss.
  • "defer <state_key>" to remind in 24 hours.

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).

Behaviour: Decline / Defer

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).

Behaviour: Re-running a Completed Wizard

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.

Implementation Notes

  • This skill is PM-invocable. The PM handles the user-facing dialog

itself and only delegates the actual install commands to the local-ops agent (per the parent protocol's Phase 3).

  • Subskill bodies are context, not procedure. They explain WHY and

document gotchas. The procedure is always defined in the parent protocol.

  • When in doubt, load migration-wizard/SKILL.md first, then the

matched subskill. The combination is authoritative.

Known Migration Subskills

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.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.