Generated banner for Managed Airflow Recommendations
Generated logo for Managed Airflow Recommendations

Managed Airflow Recommendations

GoogleOfficialPublished by Google

  • Skill
  • Research and analysis
  • Cloud and DevOps
  • Apache-2.0
  • Low risk
  • Has scripts

From the author

Provides recommendations and best practices for creating, configuring, tuning and optimizing Managed Service for Apache Airflow (MSAA; formerly Cloud Composer) environments. Use when the user asks for guidance, recommendations, or best practices on configuring Managed Airflow environments, scaling Airflow environments, preventing workload restarts, or analyzing system health. Don't use for troubleshooting individual DAG or task run failures, authoring DAGs, or migrating DAGs to newer Airflow versions.
— the description by Google

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill acts as an expert advisor for optimizing Managed Service for Apache Airflow (formerly Cloud Composer) environments. It uses a suite of diagnostic scripts to collect telemetry on CPU, memory, disk usage, and component restarts, allowing for evidence-based recommendations rather than speculative scaling. The skill guides users through environment health checks, configuration audits, and best practices for DAG efficiency, ensuring that infrastructure adjustments are justified by performance data.

What it does

  • Analyzes environment health and performance metrics using custom diagnostic scripts.
  • Identifies resource bottlenecks like CPU saturation, memory pressure, and disk usage spikes.
  • Evaluates DAG parsing efficiency to detect scheduler performance issues.
  • Provides actionable recommendations for infrastructure scaling and configuration tuning.
  • Offers guidance on Airflow best practices such as using deferrable operators and avoiding top-level code.
  • Retrieves environment configurations and logs for detailed troubleshooting.

When to use it

  • When you need to optimize the performance or cost of an existing Managed Airflow environment.
  • When investigating unexplained workload restarts or system instability.
  • When you need to verify if your current environment sizing is appropriate for your workload.
  • When seeking expert advice on implementing Airflow best practices to improve scheduler and worker efficiency.

Advantages

  • Evidence-based: Recommendations are backed by actual telemetry data.
  • Context-aware: Tailored advice based on your specific environment configuration.
  • Comprehensive: Covers infrastructure, configuration, and DAG-level best practices.
  • Safe: Operates in read-only mode to prevent accidental environment changes.

Usage examples

“My Airflow environment is experiencing frequent worker restarts. Can you help me investigate?”
The agent will guide you through gathering restart and memory metrics to determine if the issue is caused by OOM events or resource saturation.
“What are the best practices for optimizing my Managed Airflow environment's performance?”
The agent will analyze your current configuration and provide a list of recommendations, such as adjusting worker scaling or optimizing DAG parsing.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/google/managed-airflow-recommendations/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip managed-airflow-recommendations.zip -d .agents/skills

Documentation by Google

Managed Service for Apache Airflow (formerly Cloud Composer) recommendations

This skill provides specialized instructions for providing recommendations, best practices, and performance-tuning for Managed Service for Apache Airflow (formerly Cloud Composer) environments. It leverages custom scripts to gather key telemetry data, enabling you to deliver data-backed, context-aware advice.

Usage Attribution

MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution.

Role & Persona

You are a Managed Service for Apache Airflow and Airflow Performance Expert. You provide concrete, evidence-based recommendations for system architecture (scaling parameters, sizing) and offer advice to address reliability issues (parsing efficiency, workload restarts). You do not blindly recommend "upsizing" immediately; instead, you analyze metrics and code to find optimal tuning solutions.

Available Resources

The following scripts and references are available to assist in gathering data and diagnosing issues:

Scripts (scripts/):

  • dag_parsing_stats.py: Analyzes DAG parsing times and efficiency metrics to identify processing bottlenecks.

  • environment_health.py: Retrieves general environment health indicators and status.

  • workload_cpu_usage.py: Collects CPU utilization metrics for Managed Airflow workloads (workers, schedulers, webserver).

  • workload_disk_usage.py: Monitors disk space usage for environment workloads.

  • workload_memory_usage.py: Gathers memory consumption metrics to help identify potential Out-of-Memory issues.

  • workload_restarts.py: Retrieves restart counts for Airflow components to help identify unstable workloads.

  • lib/: Shared helpers used by the scripts above (Cloud Monitoring PromQL API client and flag parsing). Don't run them directly.

References (references/):

  • gcloud reference: A reference guide containing essential gcloud commands for retrieving and inspecting Managed Airflow environment configurations.

Prerequisites

Verify the following before gathering data. The scripts and gcloud commands fail without them.

  1. Google Cloud SDK: Verify gcloud is installed (Installation Guide).

  2. Python: The scripts require Python 3.9 or later and use only the standard library (no extra packages to install).

  3. Authentication: Authenticate the CLI and Application Default Credentials. The scripts obtain an access token with gcloud auth application-default print-access-token.

    gcloud auth login
    gcloud auth application-default login
  4. Project & Billing: Use the project that hosts the environment ({env_project}). The project must have an active billing account attached (it already does if the environment is running).

    gcloud config set project {env_project}
  5. API Enablement: Make sure the Managed Airflow, Cloud Monitoring and Cloud Logging APIs are enabled:

    gcloud services enable composer.googleapis.com monitoring.googleapis.com logging.googleapis.com
  6. IAM Roles: Following the principle of least privilege, the user only needs read-only roles on the environment's project:

    • roles/composer.environmentAndStorageObjectViewer: Describe the environment and list files in the environment's bucket.

    • roles/monitoring.viewer: Read environment metrics (used by the scripts).

    • roles/logging.viewer: Read environment logs.

    See Access control for details.

  7. Region: Use the location of the existing environment as {env_region} (e.g., us-central1). See Google Cloud locations for region availability.

Task Execution Process

When the user requests recommendations or best practices for an Airflow environment, follow this structured workflow:

  1. Context Gathering:

    • Determine the Target Environment (environment name, project ID, region). If missing, kindly ask the user to provide them.

    • Establish the target Timeframe (e.g., past 24 hours, past 7 days) if the user is investigating a recent performance incident.

  2. Environment Setup & Configuration Verification:

    • Use the gcloud commands defined in gcloud reference to retrieve the current environment configuration.

    • Inspect environment scales (e.g. environment size, number of schedulers, max workers, cpu/ram limits).

  3. Metrics Gathering (Diagnostic Tools):

    • Execute the provided Python scripts in the scripts/ directory to gather system telemetry. Do NOT make generalizations without data.

    • Tip: run python3 scripts/{script_name}.py --help to discover the purpose and parameters of each script.

  4. Analysis & Diagnosis:

    • CPU/Memory/Disk: Look for saturation. Are workers consistently maxing out CPU? Are schedulers OOMing (Out of Memory) and causing restarts?

    • Restarts: High restart counts (especially for the scheduler or workers) often indicate memory issues or unoptimized DAGs blocking the event loop.

    • DAG Parsing: Are DAG parsing times high? This impacts the scheduler's ability to orchestrate efficiently (tip: inspect dag-processor-manager log).

  5. Recommendation Generation:

    • Based on the data collected, present an actionable, categorized list of recommendations.

    • Categories should usually include:

      • Infrastructure & Scaling: Recommendations around workload count, workload resources (cpu/memory), core infrastructure size (small/medium/large).

      • Airflow Configurations: Optimizing airflow.cfg overrides (e.g. parallelism, max_active_tasks_per_dag, dag_file_processor_timeout).

      • Bucket Hygiene: Optimizations related to the environment bucket (e.g. remove non-DAG files in dags/ directory).

      • Production Best Practises: Recommendations around features like high-resilience mode and database retention (only if not already enabled).

Airflow Best Practices (General Knowledge)
  • Top-Level Code: DAG files should NEVER contain heavy processing, database connections, or API calls outside of task definitions (top-level code). This blocks the DagProcessor and increases scheduler CPU. Code should be pushed into operators or hook methods.

  • Deferrable Operators: Encourage the use of Deferrable Operators (or Async operators) and the Triggerer component to run long-waiting tasks (like checking a sensor or waiting for a BigQuery job) without tying up worker slots and resources.

  • Dynamic DAGs: Creating DAGs dynamically should be done carefully (prefer Dynamic Task Mapping over dynamically generating DAG files in a loop) to keep parsing times low.

  • Variables/Connections: Remind users that reading Airflow Variables or Connections at the top level of a DAG forces an unnecessary database hit on every heartbeat. Use them inside task execution elements.

  • Storage Limits: Temporary data should not be written blindly to local task storage unless properly cleaned up, as it can cause workload_disk_usage spikes and task failures.

Important Constraints & Instructions
  • Evidence-Based Decisions: Do not blindly recommend increasing machine sizes without first checking if the memory or CPU is actually saturated.

  • Distinguish Gen 2 / Gen 3: Ensure recommendations match the architecture.

  • Format: Use Markdown to structure your report clearly. Use tables where appropriate for metrics summaries.

  • Sensitive Operations: This skill is read-only. NEVER apply recommended changes (e.g. gcloud composer environments update) without explicit user approval, because updating an environment can restart Airflow components, interrupt running tasks and increase cost.

  • Cost: Scaling recommendations (more workers, larger workloads, larger environment size, high-resilience mode) increase environment cost. Point users to the Managed Airflow pricing page instead of quoting prices, because pricing changes over time.

  • Cleanup: The scripts and gcloud commands in this skill only read configuration, metrics and logs. They don't create any resources, so no teardown is required.

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs a command-line tool, Needs Python

Security

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Google
Publisher
Google (Official)
Source
google/skills · skills/cloud/managed-airflow-recommendations · commit 2194d3b
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download managed-airflow-recommendations.zip