Skip to content
TrustedSkillsbeta
Back to all skills

Migrating Dbt Project Across Platforms

Official
dbt-labs·vlatest·data·Apache-2.0

This skill seamlessly migrates your dbt projects to different cloud platforms, streamlining deployments and reducing technical hurdles for faster insights.

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 dbt-labs/dbt-agent-skills --skill migrating-dbt-project-across-platforms -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

dbt-labs

Matched to the vendor's own GitHub organisation.

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 dbt-labs/dbt-agent-skills at 0d094169f5.

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

Scanned
4 files, 508 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 a dbt (data build tool) project from one platform to another. It automates tasks like adapting connection strings, adjusting file paths, and updating configurations necessary for a successful transition. The goal is to minimize manual effort and potential errors during cross-platform dbt project migrations.

When to use it

  • Moving a dbt project from a local development environment to a cloud data warehouse (e.g., Snowflake, BigQuery).
  • Migrating a dbt project between different cloud providers.
  • Transferring a dbt project from an on-premise database to a SaaS analytics platform.
  • Updating a dbt project's underlying infrastructure or database version.

Key capabilities

  • Adapts connection strings for new environments.
  • Adjusts file paths within the dbt project.
  • Updates configuration files (e.g., dbt_project.yml).

Example prompts

  • "Migrate my dbt project from my local machine to Snowflake."
  • "Move this dbt project from BigQuery to Redshift, updating all connection details."
  • “Can you migrate this dbt project to a new version of Postgres?”

Tips & gotchas

  • Ensure the target platform is supported by the skill.
  • Review the migrated project thoroughly after execution to confirm accuracy and functionality.