cms-migration-checklist SKILL.md skillA
cms-migration-checklist from glebis/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add glebis/claude-skills/cms-migration-checklist@git:20261023.a956622Pins git:20261023.a956622 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- glebis/claude-skills
- Path
cms-migration-checklist/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261023.a956622, committed Oct 23, 2026
- First version recorded
- Oct 23, 2026
- Size
- 15,682 bytes
- Repository stars
- 410
- License
- MIT
Gated checklist and working method for migrating a WordPress site to Next.js with a Payload CMS admin — audit, owner decisions, HTML→Lexical conversion, idempotent import and reconciliation, URL/SEO parity, editorial admin, security probes, self-hosted deploy, DNS cutover, rollback and the first week after. Use this whenever someone is planning, building, reviewing or launching a WordPress → Payload (or WordPress → headless Next.js) migration, even if they only ask one slice of it. Includes a…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# WordPress → Next.js + Payload migration checklist A migration is done when **every source record has an accounted outcome, every public URL still answers, editors can publish without WordPress, and you can roll back**. A site that merely looks right can still be missing records, URLs or editorial flows, which is why the checklist is split into phases that each end in a gate with evidence. ## How to work with this skill Don't paste the whole checklist back at the user. Instead: 0. **Setup mode for a new migration.** If the user wants to start or set up a migration, or the project has no migration evidence yet, run the intake in `references/setup.md`: at most 10 questions via `AskUserQuestion` (the old site's URL or code, how much should change, URLs, body format, editorial features, plugins, hosting, audience, freeze, approver), a read-only look at the old site between rounds, and a `MIGRATION-BRIEF.md` that marks n/a items and pre-fills the decision packet. 1. **Find out where the project is.** Look for evidence before asking: an audit folder or reports (inventory, field matrix, URL manifest), a Payload config and collections, an …
Read the whole file at its exact version.
How to install
mdr add glebis/claude-skills/cms-migration-checklist@sha256:4c717ed964fcc2e4The line at the top of this page pins the label git:20261023.a956622, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_eds3ebmulcgcrtnh)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 23, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261023.a956622 latest | 2026-10-23 | a956622 | 15,682 B | A | view · diff |
| git:20261023.b06d697 | 2026-10-23 | b06d697 | 15,033 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15682 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
glebis/claude-skills · 410 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eds3ebmulcgcrtnh GET https://markdownregistry.com/api/v1/resolve?ref=glebis/claude-skills/cms-migration-checklist GET https://markdownregistry.com/api/v1/blob/4c717ed964fcc2e4f6cc7706c71019d3c0ba3789b307f6940575505b2f124059
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.