domain-migration-checklist
Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub
Walks a member through a domain-migration sign-off checklist when their site is moving from one domain to another (e.g., spellbook.legal → spellbook.com, oldbrand.com → newbrand.com). Asks 4-6 orienting questions (old domain, new domain, CMS, subdomain scope, migration window, owners), then writes a customized checklist markdown file to the active project's outputs/audits/ folder. The checklist covers 11 surface areas in three phases (Pre / During / Post) — redirects, internal links, canonicals, pre-migration cleanup, email + DNS, tracking + verification, subdomains, sitemaps + robots, schema, external listings, performance benchmarking — with per-item phase / owner / priority / status columns the member can tick off. Trigger when the user says any of "domain migration checklist", "site migration checklist", "I'm migrating my domain", "we're changing domains", "migrate from X to Y", "help me migrate my site", "domain change checklist", "rebrand migration", "switching domains", "moving to a new domain". This is a v1 STARTER — Jonathan will build a fuller domain-migration methodology / process later; this skill ships the actionable checklist now so members can stop winging migrations. Idempotent — re-running on the same project refreshes the file with current answers (prompts to confirm overwrite). Surfaces the top "do these first" Pre/P0 items in chat after writing, doesn't echo the full file. Pairs with push-changes to commit the customized checklist to the member's fork.
In this repository23 other files it gives its agents.
- connect-dataforseoSkill
- connect-emailSkill
- connect-google-cloudSkill
- connect-openaiSkill
- continue-strategySkill
- create-workerSkill
- disconnect-dataforseoSkill
- disconnect-emailSkill
- disconnect-google-cloudSkill
- disconnect-openaiSkill
- fill-project-gapSkill
- getting-startedSkill
- list-projectsSkill
- list-strategiesSkill
- load-workerSkill
- new-projectSkill
- new-strategySkill
- project-infoSkill
- project-resolverSkill
- push-changesSkill
- reload-workerSkill
- switch-projectSkill
- sync-omnipresenceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 9 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

