What is airflow-alerts-to-orchestra?

A guide for converting Airflow notifications into Orchestra alerts. Airflow is a workflow scheduler, and its notifications can be defined in callbacks, email tasks, or service-specific hooks.

Use it when an Airflow DAG sends alerts through callbacks, email, PagerDuty, or related notification operators, and you need the equivalent Orchestra configuration.

It gathers different Airflow alert patterns into Orchestra’s alert configuration, including the event status and destination. This makes it easier to preserve notifications during a migration.

airflow-alerts-to-orchestra — Skill for Claude Code by orchestra-hq

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add orchestra-hq/orchestra-skills --skill airflow-alerts-to-orchestra

Clone the repo

git clone --depth 1 https://github.com/orchestra-hq/orchestra-skills

Made for: Claude Code.

Or install migrate-to-orchestra, the plugin that ships this one along with the rest of its 52 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/airflow-alerts-to-orchestra/github.svg)](https://agentmods.dev/skills/orchestra-hq/orchestra-skills/airflow-alerts-to-orchestra)

Your own site

<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/airflow-alerts-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/airflow-alerts-to-orchestra/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/airflow-alerts-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/airflow-alerts-to-orchestra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,987 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00098	$0.01987
Opus 5.5	$0.00039	$0.00795
Sonnet 5.5	$0.00020	$0.00397
Haiku 4.5	$0.00010	$0.00199

Measured 1mo ago against content hash b821f354801b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

airflow-alerts-to-orchestra scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/migrate-to-orchestra/skills/airflow-alerts-to-orchestra/SKILL.md · 268 lines

How it starts

The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Airflow Alerts → Orchestra Alerts (All Destinations)

Overview

Airflow notifications are spread across callbacks (on_failure_callback, on_success_callback), dedicated operator tasks (EmailOperator, SlackWebhookOperator), and hooks (PagerDutyEventsHook). Orchestra consolidates all of these into a single alerts: block that can appear at the pipeline root (fires on overall pipeline status) or on individual TaskModel objects (fires on that specific task's status).

AlertModel — Full Schema

alerts:
  - name: unique-alert-name       # required, unique within scope
    statuses:                     # required, at least one
      - FAILED                    # FAILED | SUCCEEDED | CANCELLED | WARNING | SKIPPED | ANY_COMPLETED
    destinations:                 # required, at least one
      - integration: SLACK        # NotificationTypesEnum — see table below
        destination: '#channel'   # required for SLACK and EMAIL
        connection_id: null       # required for PAGER_DUTY, TEAMS, WEBHOOK, DATADOG
        parameters: null          # optional — DATADOG priority, WEBHOOK body
    custom_message: null          # optional string, max 200 chars

Destination Types — Full Reference

SLACK

destinations:
  - integration: SLACK
    destination: '#data-alerts'    # channel name or member ID — required
    # connection_id not needed — resolved from workspace-level Slack connection

EMAIL

destinations:
  - integration: EMAIL
    destination: '[email protected]'   # email address — required
    # connection_id not needed — uses Orchestra's email connection

PAGER_DUTY

destinations:
  - integration: PAGER_DUTY
    connection_id: pagerduty_conn_12345    # Orchestra PagerDuty connection — required
    # destination not used

MICROSOFT_TEAMS

destinations:
  - integration: MICROSOFT_TEAMS
    connection_id: teams_webhook_12345     # Orchestra Teams connection — required
    # destination not used

Read the full file on GitHub · 268 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed b821f354801b
2mo ago First seen · 268 lines · 98 tokens per session scan A b4a8b02301d8

Subscribe to this mod's changes

airflow-alerts-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 1,987 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Cloud DevOps and cloud

airflow-alerts-to-orchestra next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
airflow-alerts-to-orchestraorchestra-hq/orchestra-skills	Skill	9	yesterday	MIT	A	98	Claude Code
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
gke-reliabilitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	85	Claude Code, Codex
gke-workload-securitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	171	Claude Code, Codex
cloud-architectJeffallan/claude-skills	Skill	12k	7d ago	MIT	A	71	Claude Code
nemo-automodel-launcher-configNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code
azure-mgmt-botservice-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	78	Claude Code