gcp-composer-troubleshooting

Diagnose Cloud Composer DAG failures and generate root cause analysis reports.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Yashyasik/zexca-api --skill gcp-composer-troubleshooting-yashyasik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-composer-troubleshooting
Source: https://github.com/Yashyasik/zexca-api/tree/main/.gemini/skills/gcp-composer-troubleshooting
Command: npx skills add https://github.com/Yashyasik/zexca-api --skill gcp-composer-troubleshooting-yashyasik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging failed Cloud Composer (Apache Airflow) DAGs requires manually digging through logs, locating the actual remote code, and correlating errors with source lines. This Skill automates that evidence-gathering process and produces a structured Root Cause Analysis (RCA) report. ## Core Features & Use Cases - Log-Based Evidence Gathering: Uses gcloud logging with severity, DAG ID, and environment filters to find failures and stack traces. - Remote Code Retrieval: Downloads the actual DAG code running in the Composer environment via gcloud storage, avoiding assumptions based on stale local copies. - RCA Report Generation: Correlates log errors with code lines, pinpoints the root cause, proposes a fix, and saves a formal RCA report. - Use Case: A user says "My DAG daily_sales_agg failed yesterday around 2pm." The Skill fetches the failed task logs, downloads the remote DAG, identifies a KeyError at a specific line, and produces an RCA report with a recommended fix. ## Quick Start Ask the assistant to troubleshoot a failed Composer DAG by providing the DAG ID, environment name, and approximate failure time, and request an RCA report.

Frequently Asked Questions about gcp-composer-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot a failed Cloud Composer DAG?▼

Provide the DAG ID, environment name, and approximate failure time. The Skill uses gcloud logging read with severity and DAG ID filters to find errors, downloads the remote DAG code, and produces a root cause analysis with a proposed fix.

How to fetch Cloud Composer task failure logs with gcloud?▼

Use gcloud logging read with a filter like resource.type="cloud_composer_environment" combined with the environment name, dag_id label, and severity>=ERROR. The Skill applies these filters automatically and extracts tracebacks and task failure messages.

Does this skill modify my DAG code automatically?▼

No. The Skill is read-only by default: it analyzes logs and remote code, explains the root cause, and proposes a fix. It only modifies code when you explicitly ask it to apply the fix.

What happens if my local DAG differs from the remote Composer version?▼

The Skill treats the remote code as the source of truth. It asks whether to sync your local DAG to the environment or download the remote DAG into a temporary folder so the RCA is performed on the actual running code.

Why does the RCA need the remote DAG code instead of local files?▼

Local files may not match what is deployed in the Composer environment, leading to incorrect conclusions. Downloading the remote DAG from the environment's GCS bucket ensures the analysis reflects the code that actually failed.