content-migration

Move content between platforms, domains, or URL structures while preserving SEO equity, user bookmarks, and integrations. Use this skill when planning a CMS migration, replatforming, consolidating sites, changing URL structures, or merging content from multiple sources. Triggers on content migration, replatform, CMS migration, domain migration, URL restructure, redirect map, site merge, content consolidation, migration plan, post-migration drop. Also triggers when planning a launch that involves moving existing content.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear, validated multi-phase workflow and a clean one-level reference to the runbook. The main weakness is conciseness: the framework and workflow sections duplicate the same migration sequence.

Suggestions

Collapse the 'Workflow' (8 steps) section into the '6 phases' framework, or repurpose the workflow as a short bulleted checklist that explicitly references the phases instead of restating them.

Move the detailed cutover pre-flight / switch / first-24-hours content into references/migration-runbook.md and keep only a brief pointer in SKILL.md, since the runbook already covers cutover day.

Trim repetitive phrasing in the failure-patterns list (e.g., the redirect-chain and trailing-slash items overlap the URL-map rules) to a single canonical statement with a cross-reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the '6 phases' framework and the 'Workflow' (8 steps) section re-cover the same inventory->audit->map->build->test->cutover->monitor sequence, so it could be tightened; it is not the 3-anchor because not every token earns its place given that duplication.	2 / 3
Actionability	Concrete specifics abound: status codes 301/410/404, a populated URL-map table, 'Lower DNS TTL the day before (1-3 days)', 'Smoke test top 50 pages', and 'expect a temporary drop (10-30%)'; for an instruction-only skill this is copy-paste-ready guidance, matching the executable-and-specific anchor.	3 / 3
Workflow Clarity	The 6-phase sequence with pre-cutover/cutover/post-cutover checklists, explicit validation ('Verify redirects are 301 (not 302)', watch error logs), a rollback plan, and a monitor-and-recover feedback loop ('Add missed redirects from 404 patterns') meets the clear-sequence-with-explicit-validation anchor; not the 2-anchor because checkpoints are explicit.	3 / 3
Progressive Disclosure	The body is an overview that points to one real one-level-deep reference, [`references/migration-runbook.md`](references/migration-runbook.md), with its contents described and clearly signaled; no nested references, matching the well-signaled-one-level-deep anchor.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, third-person, and complete: it states concrete actions, an explicit 'Use this skill when' clause, and a broad set of natural trigger terms. It is well-scoped with low conflict risk against adjacent SEO and content skills.

Dimension	Reasoning	Score
Specificity	"Move content between platforms, domains, or URL structures while preserving SEO equity, user bookmarks, and integrations" lists multiple concrete actions and specific preservation targets, matching the 'lists multiple specific concrete actions' anchor; it is not the 2-anchor because it goes beyond naming a domain plus a few actions.	3 / 3
Completeness	It explicitly answers both what ("Move content ... while preserving SEO equity, user bookmarks, and integrations") and when ("Use this skill when planning a CMS migration..." plus the explicit trigger list), satisfying the both-what-and-when anchor; not the 2-anchor because the when is explicit, not implied.	3 / 3
Trigger Term Quality	"Triggers on content migration, replatform, CMS migration, domain migration, URL restructure, redirect map, site merge, content consolidation, migration plan, post-migration drop" covers the natural terms a user would say; it is not the 2-anchor because it includes common variations rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	The niche (content migration with SEO-equity preservation) is clear and the triggers are distinct from sibling skills like content-and-copy, seo-technical, and seo-content-audit; the minor launch overlap is scoped to 'planning a launch that involves moving existing content', so it is unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Commit: f1bc195

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.