Download for MacApple silicon, macOS 14+
Skill

gcp-managed-airflow-dag-authoring

@googlecloudplatform Updated 2026-10-23

Guides the authoring and validation of Apache Airflow DAGs for Managed Service for Apache Airflow (MSAA; formerly Cloud Composer). Covers environment context discovery, Airflow 2 vs 3 compatibility, authoring best practices, and local/remote validation processes. Use when creating or extending an Airflow DAG. Don't use when authoring Python code unrelated to Airflow DAGs.

Install

With your agent

Install OMGSkills skill "googlecloudplatform/data-agent-kit-plugin:skills/gcp-managed-airflow-dag-authoring" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/GoogleCloudPlatform/data-agent-kit-plugin /tmp/data-agent-kit-plugin && ln -s /tmp/data-agent-kit-plugin/skills/gcp-managed-airflow-dag-authoring ~/.claude/skills/gcp-managed-airflow-dag-authoring

From README

GCP Managed Airflow DAG Authoring Guide This skill guides you through authoring and validating Apache Airflow DAGs for Managed Service for Apache Airflow (MSAA; formerly Cloud Composer) environments. -------------------------------------------------------------------------------- Phase 1: Context Discovery [!IMPORTANT] Before writing any DAG code, you MUST understand the constraints (e.g. version of Airflow) and capabilities of your target environment if user is willing to provide them. 1.1 Identify Target Environment & Access Determine if you have direct access to the target Managed Airflow environment, local development environment or if you are working offline (only changing local files without validation). If environment access is available: Use gcloud to inspect the environment (see Section 1.3). If offline: Rely on user provided details. 1.2 Identify Development Environment Determine if a local development environment is available. Check if composer-dev CLI is installed.