airflow-cross-dag-to-orchestra

Use this skill when an Airflow DAG uses TriggerDagRunOperator, ExternalTaskSensor, or SubDagOperator to create cross-DAG dependencies or trigger downstream pipelines. Triggers: any DAG with external_dag_id=, trigger_dag_id=, SubDagOperator, or Airflow Datasets.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete, executable conversion examples and a clean per-pattern structure, and it respects token budget by assuming Airflow knowledge. Its main gap is the absence of an explicit validation/verification step in the migration workflow, which is notable for an operation that generates production pipeline configs.

Suggestions

Add an explicit verification step to the Before/After migration workflow, e.g. 'After conversion, validate the Orchestra YAML (orchestra validate) and test-run the triggered pipeline before relying on it.'

Note where to obtain or confirm pipeline UUIDs and how to sanity-check the trigger graph for circular dependencies during conversion, turning the Gotchas note into an actionable checkpoint.

Consider splitting the per-operator parameter reference tables into a separate REFERENCES.md file to keep SKILL.md a lean overview, since the skill exceeds 50 lines.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's Airflow competence (no 'what is a DAG' padding), jumping straight into pattern mappings with compact tables; a few explanatory asides like 'Airflow Sub-DAGs are mostly an anti-pattern' could be trimmed.	4 / 5
Actionability	Provides side-by-side executable Airflow Python and Orchestra YAML for every pattern, with complete parameter tables and copy-paste-ready examples covering the common cases (TriggerDagRunOperator, ExternalTaskSensor, SubDag, Datasets).	5 / 5
Workflow Clarity	Each pattern shows a clear before/after sequence and a full end-to-end migration example, but there is no explicit validation or verification checkpoint (e.g., validate generated YAML, test-run the triggered pipeline), which the feedback-loops note caps at 3 for pipeline-config-generating work.	3 / 5
Progressive Disclosure	No bundle files exist; the body is a single well-organized document with clear section headers per pattern and one-level-deep external doc references, though all detail is inlined rather than split into reference files.	4 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete, clearly answering both what the skill does and when to invoke it using concrete Airflow operator and identifier terms. It is concise and uses appropriate third-person trigger phrasing with no fluff.

Dimension	Reasoning	Score
Specificity	Names the Airflow cross-DAG domain and lists multiple concrete operators and patterns (TriggerDagRunOperator, ExternalTaskSensor, SubDagOperator, Datasets, cross-DAG dependencies, downstream triggering), giving comprehensive coverage of concrete actions.	5 / 5
Completeness	Explicitly states what the skill does (create cross-DAG dependencies / trigger downstream pipelines) and when to use it ('Use this skill when...' plus a 'Triggers:' clause with concrete trigger phrases).	5 / 5
Trigger Term Quality	Includes the exact terms a user working with Airflow would name — external_dag_id=, trigger_dag_id=, SubDagOperator, and Airflow Datasets — covering both operator names and code identifiers as natural trigger keywords.	5 / 5
Distinctiveness Conflict Risk	Occupies a narrow, well-defined niche (Airflow cross-DAG triggering → Orchestra) with highly specific operator-based triggers, making conflict with other skills unlikely.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: orchestra-hq/orchestra-skills
Path: skills/migrate-to-orchestra/skills/airflow-cross-dag-to-orchestra/SKILL.md
Commit: 3a29fe4

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.