Skip to content
TrustedSkillsbeta
Back to all skills

Database Migration

Checked
ovachiever·vlatest·database

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

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 ovachiever/droid-tings --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

ovachiever

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 ovachiever/droid-tings at 7acd12a754.

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

Scanned
1 file, 403 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 ensures minimal downtime during the migration. The tool supports various database systems and provides detailed progress tracking and error handling capabilities.

When to use it

  • Migrating a legacy MySQL database to PostgreSQL for improved performance.
  • Upgrading a production MongoDB instance to a newer version with breaking schema changes.
  • Consolidating data from multiple smaller databases into a single, centralized database.
  • Moving a database to a new cloud provider (e.g., AWS RDS to Google Cloud SQL).

Key capabilities

  • Schema migration
  • Data transformation
  • Downtime minimization
  • Multi-database system support
  • Progress tracking
  • Error handling

Example prompts

  • "Migrate the 'customers' database from MySQL to PostgreSQL, ensuring all data is transferred."
  • "Upgrade our MongoDB instance to version 5.0 and handle any schema incompatibilities automatically."
  • “Consolidate the ‘orders’ and ‘payments’ databases into a single ‘transactions’ database.”

Tips & gotchas

The skill requires appropriate credentials for both source and destination databases. Always test migrations in a staging environment before applying them to production data.