Lists multiple concrete actions: moving content between platforms/domains/URL structures, preserving SEO equity/bookmarks/integrations. Also references specific deliverables like redirect maps and migration plans.

Clearly answers both 'what' (move content while preserving SEO equity, bookmarks, integrations) and 'when' (explicit 'Use this skill when...' clause plus a detailed 'Triggers on' list covering multiple scenarios).

Excellent coverage of natural trigger terms users would say: 'CMS migration', 'replatforming', 'domain migration', 'URL restructure', 'redirect map', 'site merge', 'content consolidation', 'migration plan', 'post-migration drop'. These are terms practitioners naturally use.

Highly distinctive niche focused on content migration and replatforming with SEO preservation. The specific trigger terms like 'redirect map', 'CMS migration', 'domain migration', and 'post-migration drop' are unlikely to conflict with other skills.

The skill is reasonably well-structured but verbose for its audience. The 'When to use' / 'When NOT to use' sections, the extensive failure patterns list, and the near-duplication between the 6 phases and the 9-step workflow add bulk. Some content (e.g., explaining what a 301 vs 302 is, explaining why you shouldn't redirect everything to the homepage) is knowledge Claude already has. However, the domain-specific checklists and the URL map table do earn their tokens.

The skill provides structured checklists, a concrete URL map table example, and specific monitoring metrics (10-30% traffic drop, 4-8 week recovery). However, there are no executable code snippets, no specific tool commands (e.g., how to export from a CMS, how to crawl with Screaming Frog, how to implement redirects in nginx/Apache/.htaccess), and much of the guidance remains at the process/checklist level rather than copy-paste ready.

The 6-phase framework and 9-step workflow are clearly sequenced, and there are some validation checkpoints (smoke test top 50 pages, verify 301 vs 302, check search console). However, the workflow is presented twice (phases and steps) which creates ambiguity about which to follow. The validation steps are mentioned but lack explicit feedback loops (e.g., 'if smoke test fails, do X'). For a destructive/batch operation like migration, the feedback loops are insufficiently explicit.

The skill references one external file (references/migration-runbook.md) and cross-references other skills (launch-runbook, seo-content-audit, after-action-report, content-and-copy, seo-technical). However, the bundle has no actual files, and the main document is quite long (~250 lines) with content that could be split out (e.g., failure patterns, the detailed phase descriptions). The output format section and failure patterns could be separate reference files.