astro-airflow

Inspect Airflow deployments on Astro for DAG runs, task logs, and metadata.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/vanducng/skills --skill astro-airflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: astro-airflow
Source: https://github.com/vanducng/skills/tree/main/skills/astro-airflow
Command: npx skills add https://github.com/vanducng/skills --skill astro-airflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only debugging surface for Airflow on Astro. Inspect deployment state, DAG runs, task logs, container logs, and environment variables without installing an MCP plugin.

Core Features & Use Cases

  • Read-only access via the astro CLI for deployment metadata and logs
  • Retrieve Airflow DAG runs, task instance data, and logs from the deployment REST API
  • Inspect environment variables and deployment metadata to compare between environments (staging vs prod)
  • Use cases include triaging failures, auditing deployments, and validating configuration

Quick Start

Inspect a deployment with astro deployment inspect <deployment-id> and query the Airflow REST API to retrieve DAG runs.

Frequently Asked Questions about astro-airflow

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

FAQPage Schema
How do I debug failed DAG runs on Astro Airflow without installing plugins?

Debug failed DAG runs on Astro Airflow by using the astro CLI and Airflow REST API in read-only mode to retrieve DAG runs, task logs, and deployment metadata without plugins.

Can I inspect Airflow task logs and environment variables in production safely?

Yes, you can inspect Airflow task logs and environment variables in production safely because the Skill operates strictly in read-only mode to gather deployment data without modifying state.

What do I need to retrieve Airflow deployment metadata and DAG runs from Astro?

To retrieve Airflow deployment metadata and DAG runs from Astro, you need a valid deployment ID, authorized access, the astro CLI installed, and access to the deployment Airflow REST API.

How do I compare environment variables between staging and production Airflow deployments?

Compare environment variables between staging and production Airflow deployments by inspecting deployment metadata via the astro CLI to audit and validate configuration differences across environments.

What is the best way to triage failed DAGs on Astro without modifying the environment?

The best way to triage failed DAGs on Astro without modifying the environment is querying the Airflow REST API for task instance data and logs while relying on the astro CLI for deployment state.

What are the limitations of using read-only astro CLI commands for Airflow debugging?

Limitations of using read-only astro CLI commands for Airflow debugging include the inability to modify DAGs, rerun tasks, or change environment variables, as the approach strictly gathers metadata and logs.