Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    MigrateSafe

    1

    Generate a complete, reversible database migration plan as a single markdown file, with exact commands for every step, validation checks between steps, timing estimates, and a full rollback for each step.

    $19.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    MigrateSafe

    Example session with this skill installed

    Plan a Postgres 14 to Postgres 17 migration with a 30 minute downtime window, with rollback for every step and a cutover checklist.

    • Read your context and instructions
    • Compiled the migratesafe

    Migration plan: Postgres 14 to Postgres 17

    Cutover sheet

    • Strategy: dump and restore, checked against the 30 minute window with the timing model
    • Point of no return: after the target identity guards pass and the write freeze begins
    • Rehearsal gate: UNREHEARSED until a completed rehearsal is recorded

    Steps by phase

    • Pre-flight: inventory tables, indexes, sequences, enums, extensions, views, routines, triggers, partitioning, large objects, roles, grants, encoding, and collation
    • Backup: verified backup before any data movement
    • Transfer and restore: literal commands for each step, with expected success stated
    • Validation: row counts on every table, checksums on critical tables, spot samples, and your business invariants as queries on the target
    • Cutover: one page cutover checklist with a time boxed go or no go rule
    • Post-cutover: post-cutover verification and a rollback quick reference

    Rollback

    Every step has a rollback rated Clean, Costly, or Lossy, with phase rollback times and decision deadlines. Plan only: commands are written for you to run; the skill never executes them and never connects to a live database.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    For Postgres major upgrades, MySQL to Postgres, SQLite to Postgres, on prem to RDS, Supabase, or Neon, and other moves with minimal downtime. Get strategy selection by fit test, an ordered plan by phase, a one page cutover sheet, a point of no return banner, target identity guards before destructive commands, risk ratings, and a rehearsal gate. Plan only, never execute.

    Why it matters: A migration fails in the middle, not at the start. This skill treats failure as the main case: every step has a rollback, the cutover has a time boxed go or no go rule, and each step carries a risk rating so you know what to rehearse. That is the difference between a plan you can run live and a list of commands you hope will work.

    What it does:

    • Intake once, in a single short message, for source and target type and version, schema, data volume, downtime tolerance with window and time zone, target environment, every writer of the source and how each is stopped, and two or three business invariants only you know.
    • Inventory tables, indexes, sequences, enums, extensions, views, routines, triggers, partitioning, large objects, roles, grants, encoding, and collation, with a needs manual work list for anything the target cannot support natively.
    • Select strategy by computing fit tests from the timing model, dump and restore or logical replication or change capture, with both fit tests shown in the assumptions log. If neither fits, it says so plainly and offers larger window, less data first, validation after cutover with risk stated, or application dual write.
    • Draft ordered steps by phase: pre-flight, backup, transfer, restore or replicate, post-load tasks, validation, cutover, post-cutover, hold. Every step has phase, risk, reversibility, estimated time, blast radius, literal commands, expected success, validation with pass condition, rollback with state and verification, and a tell people line.
    • Attach validation after every data moving step: row counts on every table, checksums on critical tables, spot samples, plus your business invariants as queries on the target with expected results stated in advance.
    • Write a rollback for every step, rated Clean, Costly, or Lossy, with phase rollback times and decision deadlines, not only a single cutover deadline.
    • Estimate timing per step and total as low to high ranges, with assumptions stated, pre-flight and rehearsal time separate from the write freeze window, and a storage sizing block.
    • Rate risk per step, mark every Medium and High step Rehearse, and gate production plans on rehearsal: either a completed rehearsal is recorded, or the header carries UNREHEARSED with the reason.
    • Assemble one markdown plan file, with cutover sheet, strategy reason, timing summary, storage sizing, point of no return, variables block with no passwords, pre-flight checklist, steps, cutover checklist, post-cutover verification, rollback quick reference, application impact notes, and assumptions log. Then run the plan linter until it passes.

    Honest limits:

    • Plan only. It never executes migration commands. Every command is written for you to run. If you ask it to run the migration, it declines, explains that this skill plans and you or your operator executes, and hands over the exact command block for the current step with its validation and rollback. The single exception is pg_restore list on a local dump file, which only reads a local archive and never connects to a server.
    • No network and no live connections. It plans from what you supply. Version specific and platform specific claims it cannot verify are marked Verify in current documentation in the plan.
    • No secrets in the plan. Connection strings use variables without passwords. Never paste a password. If one is pasted, it is not repeated, and rotation is advised.
    • Stored routines and triggers are always flagged for manual porting across engines. It never claims automatic translation.
    • For engine pairs with no reference file, such as Oracle to Postgres or MongoDB, it still produces a plan with the same structure, says at the top that command level confidence is lower, marks every engine specific command Verify in current documentation, and prefers dump and load with heavy validation.
    • Heuristic timings are not measured timings. Rehearsal numbers replace them. A green lint check is not a substitute for timing arithmetic, fit test numbers, and Verify marks.
    • If you demand zero downtime with a large database, it says plainly that dump and restore cannot meet the window and shows the computed window that proves it. It never promises a pause shorter than the computed freeze window.

    Requirements: An agent environment that can read schema files and write markdown, with the bundled lint script runnable on the plan file. No live database connection is used.

    Example prompt: Plan a Postgres 14 to Postgres 17 migration with a 30 minute downtime window, with rollback for every step and a cutover checklist.

    What is in the package: SKILL.md, README.md, LICENSE, references including strategy guide, timing model, validation checks, rollback patterns, and pair references, examples, scripts including the plan linter, and tests.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Data & Databases.

    Plan only. It never executes migration commands and never connects to a live database. No passwords in the plan. Stored routines and triggers are flagged for manual porting across engines, never claimed as automatically translated. Heuristic timings are not measured timings; rehearsal numbers replace them.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 23 days ago

    The agent must be able to run the bundled plan lint script.

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed23 days ago

    What's inside

    Frequently Asked Questions

    Generate a complete, reversible database migration plan as a single markdown file, with exact commands for every step, validation checks between steps, timing estimates, and a full rollback for each step.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use MigrateSafe on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Data & Databases