What is fivetran-airflow-to-orchestra?

A conversion guide for replacing Airflow tasks that run Fivetran data syncs with equivalent Orchestra pipeline tasks. Airflow is a workflow scheduler, Fivetran moves data between systems, and Orchestra is another pipeline platform.

Use it to migrate Airflow code using FivetranOperator or FivetranSensor into Orchestra YAML, including connections, connector IDs, task names, and dependencies.

It explains how the settings and dependencies from the Airflow version correspond to Orchestra's format, avoiding a manual translation.

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

Your own site

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

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

When invoked 1,228 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.00090	$0.01228
Opus 5.5	$0.00036	$0.00491
Sonnet 5.5	$0.00018	$0.00246
Haiku 4.5	$0.00009	$0.00123

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

Security

Grade A, and why

fivetran-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 2mo 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/fivetran-airflow-to-orchestra/SKILL.md · 129 lines

How it starts

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

Fivetran: Airflow → Orchestra Conversion

Overview

Airflow's FivetranOperator triggers a Fivetran connector sync and optionally waits for it. FivetranSensor polls a running sync. In Orchestra the equivalent is a Sync task under the FIVETRAN integration — it triggers and waits in a single task.

Parameter Mapping

Airflow parameter	Orchestra YAML field	Notes
`fivetran_conn_id`	`connection:`	The name of the Orchestra connection to Fivetran (stores API key + secret)
`connector_id`	`parameters.connector_id`	Fivetran connector ID string — copy verbatim
`wait_for_completion=True`	(always)	Orchestra always waits
`schedule_type` / `reschedule_for`	(not needed)	Scheduling is handled by Orchestra pipeline schedule
`task_id`	`name:`	Human-readable task name
upstream `>>` chains	`depends_on:`	List upstream task names/UUIDs

Orchestra YAML Structure

version: v1
name: <pipeline-name>
pipeline:
  <stage-uuid>:
    tasks:
      <task-uuid>:
        integration: FIVETRAN
        integration_job: FIVETRAN_SYNC_ALL
        name: <task_id value from Airflow>
        connection: <orchestra-fivetran-connection-name>
        parameters:
          connector_id: <fivetran-connector-id>
        depends_on: []
        condition: null
        tags: []

Conversion Steps

Identify the Airflow task — locate FivetranOperator. Note connector_id and fivetran_conn_id.
Verify/create the Orchestra connection — in Orchestra Settings → Connections, confirm a Fivetran connection exists with your API key and secret. Note its name.
Replace operator with task block — use the YAML above.
Drop any paired FivetranSensor — Orchestra's sync task already polls.
Wire dependencies — convert >> chains to depends_on:.
Remove scheduling fields — reschedule_for, schedule_type are Fivetran-scheduler concepts; Orchestra's pipeline schedule replaces them.

Read the full file on GitHub · 129 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.

2mo ago First seen · 129 lines · 90 tokens per session scan A 562c7e95d5b1

Subscribe to this mod's changes

fivetran-airflow-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,228 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.

DevOps and cloud

fivetran-airflow-to-orchestra next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
fivetran-airflow-to-orchestraorchestra-hq/orchestra-skills	Skill	9	yesterday	MIT	A	90	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