Skip to content
TrustedSkillsbeta
Back to all skills

Database Migration

Checked
alekspetrov·vlatest·database·MIT

Helps with database, migration as part of working with databases and data persistence workflows.

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 qf-studio/navigator --skill database-migration -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

alekspetrov

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 alekspetrov/navigator at 4b2ae38d01.

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

Commit
4b2ae38d01
Manifest
skills/database-migration/SKILL.md
Scanned
1 file, 490 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

This skill automates and streamlines the process of migrating databases. It handles schema changes, data transformations, and potential conflicts between different database versions or types. The goal is to minimize downtime and ensure data integrity during these often complex operations.

When to use it

  • Upgrading a Database: You need to move from an older version of MySQL to the latest release.
  • Migrating Between Database Systems: Switching from PostgreSQL to MongoDB requires schema adjustments and data conversion.
  • Applying Schema Changes: Implementing new tables, columns, or indexes across a large database environment.
  • Data Warehouse Updates: Refreshing data in a data warehouse with transformed data from operational systems.

Key capabilities

  • Automated schema migration
  • Data transformation during migration
  • Conflict resolution
  • Database version compatibility handling

Example prompts

  • "Migrate the 'customers' table from MySQL 5.7 to PostgreSQL 14, ensuring all data is converted correctly."
  • "Apply the latest schema changes defined in migration_script.sql to our production database."
  • “Can you migrate our legacy Oracle database to a cloud-based Snowflake instance?”

Tips & gotchas

The skill requires access credentials and connection details for both the source and destination databases. Always test migrations on a staging environment before applying them to production data.