New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Site Migration

by textura-agency in textura-agency/next16-claude-starter

Protect search rankings when rebuilding or relaunching an existing site — pre-migration crawl and inventory, rankings snapshot, redirect map, and post-launch verification.

UnlicenseAuto-check: notes

Install Site Migration

skills CLI
$ npx skills add textura-agency/next16-claude-starter --skill site-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install textura-agency/next16-claude-starter site-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/textura-agency/next16-claude-starter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/site-migration .claude/skills/site-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
site-migration
GitHub stars
133
Token cost
~1k tokens
SKILL.md length
545 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
Unlicense

At a glance

Protect search rankings when rebuilding or relaunching an existing site — pre-migration crawl and inventory, rankings snapshot, redirect map, and post-launch verification.

  • Works in 6 steps: Inventory the live site — before… → Snapshot what you are protecting → Build the redirect map → …
  • The user is rebuilding a live site
  • SKILL.md covers 1. Inventory the live site —…, 2. Snapshot what you are…, 3. Build the redirect map and 4. Carry over what search…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Site Migration is an agent skill from textura-agency/next16-claude-starter. Protect search rankings when rebuilding or relaunching an existing site — pre-migration crawl and inventory, rankings snapshot, redirect map, and post-launch verification. Use when the user is rebuilding a live site, replacing an existing site, changing URL structure, or says "we're relaunching", "migrating from WordPress/Webflow", or "will this hurt our rankings".

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with WordPress and Webflow. The repository describes itself as: AI-first Next.js 16 starter for animation-heavy sites, wired with an Obsidian vault & Claude Code hooks. The licence is Unlicense.

When your agent uses it

  • The user is rebuilding a live site
  • Replacing an existing site
  • Changing URL structure
  • Says were relaunching

Example prompts

  • “re relaunching”
  • “migrating from WordPress/Webflow”
  • “will this hurt our rankings”
  • “/site-migration”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, WebFetch, WebSearch

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Inventory the live site — before anything changes
  2. Snapshot what you are protecting
  3. Build the redirect map
  4. Carry over what search engines already trust
  5. Launch checklist
  6. After launch

What it can do on your machine

Read from SKILL.md and the folder at commit 6c6edf9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • Edit
    • WebFetch
    • WebSearch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Site Migration loads about 1k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 545 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~96
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, Edit, WebFetch, WebSearch

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from textura-agency/next16-claude-starter at commit 6c6edf9, republished under its Unlicense licence (© textura-agency). 545 words, ~1,005 tokens.

Download SKILL.mdSave it as .claude/skills/site-migration/SKILL.md (or your agent's skills folder).
name
site-migration
description
Protect search rankings when rebuilding or relaunching an existing site — pre-migration crawl and inventory, rankings snapshot, redirect map, and post-launch verification. Use when the user is rebuilding a live site, replacing an existing site, changing URL structure, or says "we're relaunching", "migrating from WordPress/Webflow", or "will this hurt our rankings".
allowed-tools
Bash, Read, Write, Edit, WebFetch, WebSearch

Site migration without losing rankings

Traffic collapse after a relaunch is almost always the same cause: URLs changed and nothing told search engines where they went. The work below happens before the new site goes live. After launch it is damage control.

If the user is rebuilding a live site, raise this at the start of the project, not at the end. It is the cheapest insurance in the whole engagement.

1. Inventory the live site — before anything changes

Crawl or list every indexed URL. Record: URL, page title, H1, content type, whether it currently ranks. Save to MIGRATION-URL-INVENTORY.md.

Sources, in order of reliability: the existing sitemap.xml, Search Console's Pages report, an actual crawl, the CMS's own page list. Use several — each misses different things, and the ones they miss (old landing pages, PDFs, paginated archives) are exactly the ones that quietly carry links.

2. Snapshot what you are protecting

Ask the user for a Google Search Console performance export (last 3–6 months: Performance → Export). From it record:

  • top 20 pages by clicks
  • top 30 queries by clicks and impressions
  • everything ranking in positions 1–10

Save to MIGRATION-RANKINGS-SNAPSHOT.md. This is the baseline you will be judged against, so capture it before the rebuild touches anything.

Also capture the most-linked pages (Ahrefs/Semrush export if they have one). A page with backlinks must keep its equity — losing it is far more expensive than losing an unlinked page.

3. Build the redirect map

MIGRATION-REDIRECT-MAP.md, two columns: old URL → new URL. Rules:

  • Every old URL gets a destination. Mark unknowns [TBD] and resolve them all before launch — a [TBD] at launch is a 404.
  • Map to the closest equivalent page, never blanket-redirect everything to the homepage. Google treats mass homepage redirects as soft 404s and the equity is lost.
  • 301 (permanent), not 302, unless the change genuinely is temporary.
  • One hop. Chained redirects leak and slow crawling — if the old site already redirects, map to the final destination.
  • Preserve query-parameter and trailing-slash behaviour, or normalise it deliberately and consistently.

In this starter, redirects live in next.config.ts (redirects()), or at the platform edge if the volume is large. Keep them in code so they are reviewable.

Show full SKILL.md (184 more words)Show less

4. Carry over what search engines already trust

  • Keep URL structure identical wherever there is no strong reason to change it. "The new IA is nicer" is rarely worth the risk on a ranking page.
  • Preserve page titles and H1s on pages that rank, unless improving them is the point.
  • Carry over the content — a rebuilt page with a third of the copy usually drops.
  • Keep the same canonical/lang conventions; re-add structured data.

5. Launch checklist

  • Every old URL redirects, one hop, 301, to a real page
  • robots.ts allows crawling (staging blocks removed — check this twice)
  • sitemap.ts lists every new public route, and is submitted in Search Console
  • NEXT_PUBLIC_SITE_URL points at the production domain
  • No noindex left over from staging
  • Analytics and Search Console verified on the new site
  • Core Web Vitals measured on the new site (seo-audit skill)

6. After launch

Watch weekly for the first month: Search Console coverage errors, 404s in logs, and the ranking snapshot from step 2. Some fluctuation for 2–4 weeks is normal; a sustained drop on a specific page means its redirect or its content is wrong.

© textura-agency, Unlicense. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/site-migration of textura-agency/next16-claude-starter.

Open the folder on GitHubat commit 6c6edf9

Compare with similar skills

Site Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Site Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Site Migration this skilltextura-agency/next16-claude-starter133—~1kAutomated safety check: NotesUnlicense
Cms Migrationpayloadcms/skills1631 repos~1.3kAutomated safety check: PassNone
Sanity Migrationsanity-io/agent-toolkit188—~1.4kAutomated safety check: PassMIT
Content Management Systemsgithub/awesome-copilot40k1 repos~1.3kAutomated safety check: PassMIT
Citation Recovery Optimizeramplitude/builder-skills159—~3.3kAutomated safety check: PassNone
Webflow Migration Deep Divejeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Cms Migration

    payloadcms/skills

    A skill your agent uses when user wants to migrate content from another CMS (WordPress, Contentful, Strapi, Sanity, Webflow, etc.) to Payload CMS

    163 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

  • Sanity Migration

    sanity-io/agent-toolkit

    Official

    Plans, implements, and reviews migrations from other CMSes and content systems into Sanity.

    188 GitHub stars~1.4k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

  • Content Management Systems

    github/awesome-copilot

    Official

    Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and…

    40k GitHub starsUsed in 1 repo~1.3k tokens
    Sales & SupportAuto-check passed

  • Citation Recovery Optimizer

    amplitude/builder-skills

    A skill your agent uses whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI…

    159 GitHub stars~3.3k tokensUpdated 2 mo ago
    Research & ScienceAuto-check passed

  • Webflow Migration Deep Dive

    jeremylongshore/tons-of-skills-marketplace

    Migrate external or cross-site content into Webflow CMS with schema mapping, staged batches, reconciliation, and controlled publication.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed

  • Publish Blog

    indranilbanerjee/digital-marketing-pro

    Publish a blog post to WordPress or Webflow with SEO metadata, approval-gated.

    862 GitHub starsUsed in 1 repo~2.9k tokens
    Writing & ContentAuto-check passed

More from textura-agency/next16-claude-starter

All 16 skills in this repo

  • Mobile Device QA

    textura-agency/next16-claude-starter

    Make a site behave on real phones — the defects no Lighthouse run or headless scroll test sees, learned from site owners reviewing production sites on an iPhone.

    135 GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes

  • Optimize Load

    textura-agency/next16-claude-starter

    Get a page into Lighthouse's green zone on desktop and mobile, for people AND for the robot form crawlers get — build it, audit all four categories (Performance, Accessibility, Best Practices, SEO)…

    135 GitHub stars~4.6k tokensUpdated yesterday
    Auto-check: notes

  • Optimize Performance

    textura-agency/next16-claude-starter

    Make a page in this starter actually smooth — build it, scroll it in real Chrome on PC and on an emulated phone, fix what the measurement blames, re-measure to prove it.

    135 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check: notes

  • Payload Admin

    textura-agency/next16-claude-starter

    Make a Payload admin feel like part of the site and explain itself — the skin re-tinted from the site's own tokens (calm, light, no added motion), the site's wordmark and favicon, a dashboard…

    135 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Payload Cms

    textura-agency/next16-claude-starter

    Put a Payload CMS admin on a site built from this starter — every visible string and content photo editable, derived from the site's own content objects with the code's copy as the fallback, a…

    135 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check: notes

  • Aeo Visibility

    textura-agency/next16-claude-starter

    Answer Engine Optimisation — make the site citable by ChatGPT, Claude, Perplexity, Gemini and AI Overviews.

    135 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check: notes

Works with

Questions about Site Migration

What does Site Migration do?

Protect search rankings when rebuilding or relaunching an existing site — pre-migration crawl and inventory, rankings snapshot, redirect map, and post-launch verification. Site Migration is an agent skill from textura-agency/next16-claude-starter. Protect search rankings when rebuilding or relaunching an existing site — pre-migration crawl and inventory, rankings snapshot, redirect map, and post-launch verification.

When should I use Site Migration?

Site Migration fits situations like: the user is rebuilding a live site; replacing an existing site; changing URL structure; says were relaunching.

How do I install Site Migration in Claude Code?

Run `npx skills add textura-agency/next16-claude-starter --skill site-migration -a claude-code`. Or copy the skill folder (.claude/skills/site-migration in textura-agency/next16-claude-starter) into .claude/skills/site-migration in your project. Claude Code loads it when a task matches its description.

How do I install Site Migration in Codex?

Run `npx skills add textura-agency/next16-claude-starter --skill site-migration -a codex`. Or copy the skill folder (.claude/skills/site-migration in textura-agency/next16-claude-starter) into .agents/skills/site-migration in your project. Codex loads it when a task matches its description.

Can I use Site Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add textura-agency/next16-claude-starter --skill site-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/site-migration, .gemini/skills/site-migration, .github/skills/site-migration and .opencode/skills/site-migration in your project.

What does Site Migration need to run?

SKILL.md names no scripts, command-line tools or credentials: Site Migration is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, WebFetch, WebSearch.

Does Site Migration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Site Migration safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Site Migration use?

Site Migration is published under the Unlicense licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Site Migration use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Site Migration?

Skills that share tags, products or a category with Site Migration: Cms Migration (payloadcms/skills, 163 stars), Sanity Migration (sanity-io/agent-toolkit, 188 stars), Content Management Systems (github/awesome-copilot, 40k stars) and Citation Recovery Optimizer (amplitude/builder-skills, 159 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Site Migration?

textura-agency (a GitHub organization) maintains it in textura-agency/next16-claude-starter, which has 133 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 7, 2026.

Source: textura-agency/next16-claude-starter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.