Skip to content
TrustedSkillsbeta
Back to all skills

Migrate Site

Checked
calm-north·vlatest·other·MIT

Seamlessly moves websites to new hosting environments while preserving data and functionality, powered by calm-north.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add calm-north/seojuice-skills --skill migrate-site -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

calm-north

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned calm-north/seojuice-skills at c1f633bea5.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c1f633bea5
Manifest
skills/migrate-site/SKILL.md
Scanned
1 file, 206 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The migrate-site skill enables AI agents to assist with website migration tasks, such as transferring content, configurations, and data from one platform or hosting environment to another. It supports handling common challenges like preserving SEO settings, redirect mappings, and ensuring continuity of user experience during the transition.

When to use it

  • Migrating a WordPress site to a new host while maintaining existing SEO rankings
  • Transferring content from an old CMS to a modern platform with minimal downtime
  • Setting up redirects after rebranding or restructuring a website

Key capabilities

  • Automates content and configuration transfer between platforms
  • Preserves SEO metadata and redirect rules during migration
  • Supports multiple hosting environments and CMS systems

Example prompts

  • "Migrate my WordPress site to Bluehost while keeping all SEO settings intact."
  • "Transfer blog posts and media from Squarespace to a new Ghost instance."
  • "Set up 301 redirects for pages that have changed URLs during the migration."

Tips & gotchas

  • Ensure backups are made before initiating any migration process.
  • Some advanced configurations may require manual review after automation to ensure accuracy.