astro-airflowlisted

# astro-airflow Read-only debugging surface for Airflow on Astro. No MCP plugin install required — uses `astro` CLI for what it exposes (container logs, env vars, deployment metadata) and `curl` against the deployment's Airflow REST API for what it doesn't (DAG runs, task instance logs). ## When to use - User asks "what failed in `<dag_id>`" or "why is `<dag_id>` stuck" on staging/prod - User says "check the deployment logs", "fetch task log", "clear failed tasks" on Astro - User references an Astro deployment ID (e.g. `cmgjr4hyl001l01lrepyhz604`) or a `*.astronomer.run/<id>` URL - A repo's CLAUDE.md mentions Astro deployments, `make airflow CMD=...`, or `astro dev start` - Need to compare staging vs prod env vars / connections / variables - Debugging a CI deploy that hit Astronomer **When NOT to use:** local-only Airflow questions where `make airflow CMD=...` or the local Astro container suffices — use those directly. This skill is for *remote* (staging/prod) inspection. ## Prerequisites - `astro` CLI installed and logged in (`astro login <org-hostname>`) — verify with `astro context list` - `curl` and `jq` (both standard) - A **Deployment API token** for the target deployment, stored in gopass. Mint via Astro UI → Deployment → Access → API Tokens. Use a custom least-privilege role with `deployment.get` + `deployment.airflow.*.get` permissions for read-only debugging. - Deployment **webserver URL** (e.g. `https://<org>.astronomer.run/<deployment-short-id>/`) — find via