Skip to content
TrustedSkillsbeta
Back to all skills

Data Layer Migration

Checked
blazity·vlatest·database

Helps with data, migration as part of agent workflows 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 blazity/next-migration-skills --skill data-layer-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

blazity

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 blazity/next-migration-skills at 5181f8874c.

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

Commit
5181f8874c
Manifest
skills/data-layer-migration/SKILL.md
Scanned
1 file, 247 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 facilitates the migration of data layers, likely involving transferring data between different storage systems or formats. It automates aspects of this process to reduce manual effort and potential errors. The specific details of supported data layer types and migration strategies are not provided in the source content.

When to use it

  • Moving a database from one provider to another (e.g., MySQL to PostgreSQL).
  • Upgrading a legacy data storage format to a newer, more efficient version.
  • Consolidating data from multiple sources into a single data layer.
  • Migrating data as part of a larger application refactoring effort.

Key capabilities

  • Automated data layer migration
  • Support for various data layer types (specifics not detailed)
  • Error handling and reporting during the migration process

Example prompts

  • "Migrate the customer database from MySQL to PostgreSQL."
  • "Upgrade our legacy data format to version 3.0."
  • "Consolidate sales data from both regions into a single data layer."

Tips & gotchas

The skill's effectiveness depends on compatibility between source and destination data layers; ensure these are supported before initiating migration. Detailed documentation regarding specific configuration options or limitations is not available in the provided source.