When the user wants to create, optimize, or audit migration guides for users switching from competitors. Also use when the user mentions "migration guide," "migrate from X," "switch to [product]," "import from X," or "data migration." For rebrand and redirects, use rebranding-strategy.
Guides migration pages that help users switch from a competitor to your product. Reduces friction for switchers; often linked from alternatives pages. Common for SaaS, tools, and productivity apps.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, migration capabilities, and source platforms.
Identify:
| Section | Purpose | |---------|---------| | Headline | "Migrate from [Competitor] to [Product] in Minutes" | | Why switch | Brief; link to alternatives for full comparison | | What transfers | Data, structure, attachments; what's supported | | Steps | Numbered guide; screenshots or video | | Troubleshooting | Common issues, support link | | CTA | Start migration, try free, contact support |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/migration · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/migration"
cp -r "skills/pages/marketing/migration" ".claude/skills/migration"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.