/migration
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
$ npx -y skills add kostja94/marketing-skills --skill migration --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/migration
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
migration.SKILL.mdname: migration-page-generator
description: 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.
metadata:
version: 1.0.1
Pages: Migration
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.
Initial Assessment
**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: 1. **Source**: Which competitor(s) to cover (Notion, Trello, etc.) 2. **Format**: Single hub vs. per-competitor pages (/migrate-from-notion) 3. **Migration type**: Manual import, automated tool, API 4. **Primary goal**: Sign up, start migration, reduce churn risk
Page Structure
| 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 |
Best Practices
Clarity
- **Explicit steps**: "1. Export from X. 2. Upload to [Product]. 3. Map fields."
- **Time estimate**: "Takes ~10 minutes for most workspaces"
- **Data scope**: What transfers; any limitations
Trust
- **No competitor bashing**: Focus on your product's ease
- **Support**: Offer help; link to docs, chat, email
- **Success stories**: "10,000+ teams migrated from X"
SEO
- **Intent**: Transactional; "migrate from X to Y"
- **Title**: "Migrate from [Competitor] to [Product] | Step-by-Step Guide"
- **Internal links**: Alternatives, features, pricing, docs
Output Format
- **Headline** and intro
- **Step-by-step** migration guide
- **Data transfer** scope
- **Troubleshooting** section
- **Internal links**
- **SEO** metadata
Related Skills
- **alternatives-page-generator**: Link to migration from alternatives
- **docs-page-generator**: Detailed migration docs
- **landing-page-generator**: Migration as conversion page
- **faq-page-generator**: Migration FAQ section
Read more
name: migration-page-generator description: 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. metadata: version: 1.0.1
Pages: Migration
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.
Initial Assessment
**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: 1. **Source**: Which competitor(s) to cover (Notion, Trello, etc.) 2. **Format**: Single hub vs. per-competitor pages (/migrate-from-notion) 3. **Migration type**: Manual import, automated tool, API 4. **Primary goal**: Sign up, start migration, reduce churn risk
Page Structure
| 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 |
Best Practices
Clarity
- **Explicit steps**: "1. Export from X. 2. Upload to [Product]. 3. Map fields."
- **Time estimate**: "Takes ~10 minutes for most workspaces"
- **Data scope**: What transfers; any limitations
Trust
- **No competitor bashing**: Focus on your product's ease
- **Support**: Offer help; link to docs, chat, email
- **Success stories**: "10,000+ teams migrated from X"
SEO
- **Intent**: Transactional; "migrate from X to Y"
- **Title**: "Migrate from [Competitor] to [Product] | Step-by-Step Guide"
- **Internal links**: Alternatives, features, pricing, docs
Output Format
- **Headline** and intro
- **Step-by-step** migration guide
- **Data transfer** scope
- **Troubleshooting** section
- **Internal links**
- **SEO** metadata
Related Skills
- **alternatives-page-generator**: Link to migration from alternatives
- **docs-page-generator**: Detailed migration docs
- **landing-page-generator**: Migration as conversion page
- **faq-page-generator**: Migration FAQ section
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill