How do I install the Meta Migration Assistant skill?

Run npx skillmds@latest add gabrielmoreira/meta-migration-assistant in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Meta Migration Assistant safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Meta Migration Assistant?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Meta Migration Assistant free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Meta Migration Assistant?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Meta Migration Assistant by gabrielmoreira

Name: Meta Migration Assistant
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Meta Migration Assistant

Use this meta-skill instead of answering directly when the user needs a concrete migration plan that benefits from multi-skill orchestration across migration classification, authoritative guide lookup, optional repo diff inspection, and step-by-step validation planning.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

Migration Assistant (Meta-Skill)

Take a "help me migrate X → Y" request and produce a concrete, runnable checklist. The pipeline does four things:

classify the migration kind via an LLM tag (one of six tokens).

fetch_guide the most authoritative source for THAT migration:

Classifier verdict	Best source	Routed skill
`OPENAI_V0_TO_V1`	repo release notes	`github`
`PY2_TO_PY3`	framework migration doc	`multi-search-engine`
`VUE2_TO_VUE3`	framework migration doc	`multi-search-engine`
`REACT_CLASS_TO_HOOKS`	framework migration doc	`multi-search-engine`
`CJS_TO_ESM`	(fuzzy, synthesize)	`multi-search-engine`
`OTHER` (default)	(synthesize)	`deep-research`

repo_context optionally inspects the current repo diff only when the prompt indicates that local repository context should shape the migration.
write_plan uses a constrained llm_chat renderer so explicit source and target terms in the user request remain authoritative even when repository context or retrieved guide text is noisy.

Fallback

If the orchestration fails: ask the user to specify the migration tag manually, run the matching skill yourself, then write the checklist.

Frequently asked questions