360 Secure SkillHub
360 安全技能中心

migration-page-generator

面向从竞品切换到自身产品的用户,生成迁移指南页面:先确认源平台、单页还是按竞品分页、迁移方式与主要目标,再输出标题与引言、切换理由、可迁移数据范围、分步操作指南、故障排查、行动号召、内链建议与 SEO 元数据,并强调步骤清晰与信任建设。

kostja94
kostja94
热度 47.43
最近更新 2026-05-11 17:35:23
分类:营销依赖:纯提示词应用场景:文案创作 / 模板

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add migration-page-generator
Metadata
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