What problem does it solve? When a Cloud Composer (Apache Airflow) DAG fails, finding the root cause requires digging through scattered logs and verifying which code version actually ran. This Skill guides an evidence-based Root Cause Analysis (RCA) workflow that fetches remote logs and code before proposing any fix. ## Core Features & Use Cases - Log-Based Evidence Gathering: Uses gcloud logging read with severity, environment, and DAG ID filters to locate failures and stack traces. - Remote Code Retrieval: Downloads the actual DAG code from the Composer GCS bucket via gcloud storage, treating remote code as the source of truth rather than assuming local files match. - RCA Report Generation: Correlates log errors with specific code lines, explains the root cause, proposes a fix, and produces a saved RCA report. - Pipeline Template Validation: Provides compliant deployment.yaml and orchestration-pipeline.yaml templates for declarative pipelines (dbt, PySpark, BigQuery actions). - Use Case: A user says "My DAG daily_sales_agg failed yesterday around 2pm." The Skill queries Composer logs, finds a KeyError: 'region' in the failed task, downloads the remote DAG, pinpoints line 45, and generates an RCA report with a recommended fix. ## Quick Start Ask the agent to troubleshoot why your Cloud Composer DAG failed and generate a Root Cause Analysis report, providing the DAG ID and approximate failure time.