Skip to content
TrustedSkillsbeta
Back to all skills

Migrating Airflow 2 To 3

Checked
astronomer·vlatest·data·Apache-2.0

This skill seamlessly migrates your existing Airflow 2 DAGs and configurations to Airflow 3, streamlining upgrades and leveraging new features.

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 astronomer/agents --skill migrating-airflow-2-to-3 -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

astronomer

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 astronomer/agents at cbe1141f54.

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

Commit
cbe1141f54
Manifest
skills/migrating-airflow-2-to-3/SKILL.md
Scanned
5 files, 1,019 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 helps users migrate Apache Airflow workflows from version 2 to version 3, including updating DAGs, plugins, and configurations for compatibility with the new version. It provides guidance on handling deprecated features, upgrading dependencies, and ensuring smooth operation in the upgraded environment.

When to use it

  • You are planning an upgrade of your Airflow instance from version 2.x to 3.x.
  • Your existing DAGs or plugins are incompatible with Airflow 3 due to changes in APIs or configurations.
  • You need assistance identifying and fixing breaking changes during the migration process.

Key capabilities

  • Detects deprecated features in Airflow 2 DAGs and suggests replacements for Airflow 3.
  • Provides step-by-step guidance on updating plugins, dependencies, and configuration files.
  • Offers best practices for testing and validating workflows post-migration.

Example prompts

  • "Help me migrate my Airflow 2 DAG to version 3."
  • "What changes do I need to make in my Airflow config file when upgrading from 2 to 3?"
  • "How can I test my migrated Airflow 3 DAGs for compatibility?"

Tips & gotchas

  • Ensure all third-party plugins are compatible with Airflow 3 before starting the migration.
  • Always back up your current Airflow setup and test migrations in a staging environment first.