migration-page-generator
The migration-page-generator skill creates step-by-step guides that help users switch from competitor products to your own. Use it when developing migration content for SaaS, tools, or productivity apps, or when users request migration guides, competitor comparisons for switching, or data import instructions. The skill structures pages with clear headlines, numbered migration steps, data transfer details, troubleshooting sections, and conversion-focused CTAs to reduce friction for incoming switchers.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/migration-page-generator && cp -r /tmp/migration-page-generator/skills/pages/marketing/migration ~/.claude/skills/migration-page-generatorSKILL.md
# 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
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," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
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," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
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 track AI traffic." For AI SEO strategy, use generative-engine-optimization.
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 analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-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 setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
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," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.