migrating-dagster-to-airflow

Guide for migrating Dagster projects to Apache Airflow 3 on Astro. Use when the user mentions migrating, converting, or porting Dagster (or Dagster+) code to Airflow or Astro, wants to plan or assess such a migration, or asks what a Dagster construct maps to in Airflow. Covers assets, partitions, schedules, sensors, declarative automation, resources, IO managers, ops/jobs, dbt, Pipes, Components, and Dagster+ platform config. Always load this skill as the first step for any Dagster-to-Airflow request.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%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.

A tightly written, highly actionable migration playbook with excellent workflow sequencing and validation feedback loops. Its one real defect is bundle completeness: the body depends on 11 reference/*.md files that are absent, so progressive disclosure breaks at load time.

Suggestions

Ship the missing reference/ files referenced by the routing table (quickstart.md, mapping.md, assets.md, io-and-data-passing.md, partitions.md, automation.md, dbt.md, components.md, astro-deployment.md, validation.md, troubleshooting.md) — every phase currently routes to files that don't exist.

If some references are intentionally deferred, mark them as such in the routing table so the agent doesn't follow dead links expecting detail.

Verify the reference/ vs references/ path spelling matches the actual bundle directory name to avoid silent path mismatches.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout; assumes Claude's competence with no padding about what Dagster/Airflow are, and every section (Hard rules, Phases 0-7, routing table) earns its tokens.	5 / 5
Actionability	Provides copy-paste-ready commands tied to real scripts ('python3 scripts/inventory.py <dagster_repo> --out manifest.json', 'python3 scripts/validate_dag.py', 'status.py advance <unit-id>'), all of which exist in scripts/.	5 / 5
Workflow Clarity	Phases 0-7 are explicitly sequenced with validation gates, a per-unit state machine, feedback loops (retry ~10 attempts then defer; status.py reopen), and a nonzero-exiting completeness gate — exactly the validate-fix-retry pattern for destructive/batch cutover work.	5 / 5
Progressive Disclosure	The routing table cleanly signals one-level-deep references, but the entire reference/ directory is missing — all 11 referenced files (quickstart.md, mapping.md, assets.md, partitions.md, automation.md, dbt.md, components.md, astro-deployment.md, validation.md, troubleshooting.md, io-and-data-passing.md) are dead links in the actual bundle, so navigation fails in practice.	3 / 5
	Total	18 / 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.

A strong, third-person description that clearly states the skill's purpose, lists comprehensive capabilities, and provides explicit, natural trigger phrases for when to load it. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete capabilities — 'assets, partitions, schedules, sensors, declarative automation, resources, IO managers, ops/jobs, dbt, Pipes, Components, and Dagster+ platform config' — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both what ('Guide for migrating Dagster projects to Apache Airflow 3 on Astro') and when ('Use when the user mentions migrating, converting, or porting...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers natural synonyms users would say — 'migrating, converting, or porting', 'Dagster (or Dagster+)', 'Airflow or Astro', 'plan or assess', 'maps to in Airflow' — with strong variation coverage.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Dagster-to-Airflow/Astro migration) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: astronomer/agents
Path: skills/migrating-dagster-to-airflow/SKILL.md
Commit: dbd9bb7

Reviewed: ~22 hours 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.