What is slack-airflow-to-orchestra?

A migration guide for changing Airflow Slack notifications into equivalent Orchestra alerts or Slack-sending tasks. Airflow is a workflow tool, and a DAG is its definition of a set of scheduled tasks and their order.

Converting Airflow success and failure callbacks, Slack operators, and Python tasks that post messages into Orchestra configurations.

It distinguishes status callbacks from actual pipeline steps, so notifications keep the right timing and do not become unnecessary tasks.

slack-airflow-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 slack-airflow-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/slack-airflow-to-orchestra/github.svg)](https://agentmods.dev/skills/orchestra-hq/orchestra-skills/slack-airflow-to-orchestra)

Your own site

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

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

When invoked 2,229 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.00163	$0.02229
Opus 5.5	$0.00065	$0.00892
Sonnet 5.5	$0.00033	$0.00446
Haiku 4.5	$0.00016	$0.00223

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

Security

Grade A, and why

slack-airflow-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/slack-airflow-to-orchestra/SKILL.md · 217 lines

How it starts

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

Slack: Airflow → Orchestra Conversion

Overview

Airflow Slack notifications come in two forms:

Callback functions (on_failure_callback, on_success_callback) — not DAG tasks; fire when a task or DAG changes status.
Explicit DAG tasks (SlackWebhookOperator, SlackAPIPostMessageOperator, or a plain PythonOperator/@task that calls slack_sdk.WebClient(...).chat_postMessage(...) directly) — pipeline steps that send a message at a specific point. A task doesn't need to use a dedicated Slack operator to count here — if its whole job is formatting and posting a Slack message, treat it as form 2, not generic Python.

In Orchestra, Slack notifications are handled two ways:

alerts block (pipeline-level or task-level) — fires on status change; no pipeline slot consumed.
SLACK pipeline task (integration: SLACK, integration_job: SEND_SLACK_MESSAGE) — fires at a specific DAG position, useful when content depends on runtime logic or ordering matters.

Decision Guide

Airflow pattern	Orchestra equivalent
`on_failure_callback` / `on_success_callback` on `default_args` or task	Pipeline-level or task-level `alerts` YAML block
`SlackWebhookOperator` at the end of a DAG (completion notification)	Pipeline-level `alerts` YAML block
`SlackWebhookOperator` mid-DAG (status update between tasks)	`SLACK` + `SEND_SLACK_MESSAGE` pipeline task OR task-level `alerts` block

Option 1: Orchestra Alerts (YAML) — recommended for callbacks & completion notifications

Alerts live in the alerts key at the top level of the pipeline YAML. Orchestra fires them when the pipeline reaches any of the listed statuses.

AlertModel schema

Field	Type	Required	Notes
`name`	string	✅	Unique within the pipeline
`statuses`	array	✅	`FAILED`, `SUCCEEDED`, `CANCELLED`, `WARNING`, `SKIPPED`
`destinations`	array	✅	One entry per channel/target
`custom_message`	string	❌	Appended to the standard Orchestra alert message

Read the full file on GitHub · 217 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 d98fe2d9aab6
2mo ago First seen · 217 lines · 163 tokens per session scan A aa05b07fee46

Subscribe to this mod's changes

slack-airflow-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed yesterday), licensed MIT. It adds 163 tokens to every session and 2,229 once invoked, about $0.0007 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.

DevOps and cloud

slack-airflow-to-orchestra next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
slack-airflow-to-orchestraorchestra-hq/orchestra-skills	Skill	9	yesterday	MIT	A	163	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code