migrating-airflow-2-to-3
Guide for migrating Apache Airflow 2.x projects to Airflow 3.x. Use when the user mentions Airflow 3 migration, upgrade, compatibility issues, breaking changes, or wants to modernize their Airflow codebase. If you detect Airflow 2.x code that needs migration, prompt the user and ask if they want you to help upgrade. Always load this skill as the first step for any migration-related request.
89
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description with excellent trigger terms and completeness, clearly specifying both what the skill does and when to use it. Its main weakness is that the 'what' portion could be more specific about the concrete migration actions performed (e.g., updating imports, replacing deprecated APIs, modifying DAG definitions). The proactive detection guidance is a nice touch that adds practical value.
Suggestions
Add specific concrete migration actions to improve specificity, e.g., 'Handles updating deprecated operators, migrating import paths, adapting DAG definitions, and resolving API breaking changes between Airflow 2.x and 3.x.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Airflow 2.x to 3.x migration) and mentions some actions like detecting Airflow 2.x code and prompting the user, but it doesn't list specific concrete migration actions (e.g., updating DAG definitions, replacing deprecated operators, updating import paths, handling API changes). | 2 / 3 |
Completeness | Clearly answers both 'what' (guide for migrating Airflow 2.x to 3.x) and 'when' (explicit 'Use when...' clause listing multiple trigger scenarios including migration, upgrade, compatibility issues, breaking changes, and modernization). Also includes proactive detection guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Airflow 3 migration', 'upgrade', 'compatibility issues', 'breaking changes', 'modernize', 'Airflow codebase', and 'Airflow 2.x code'. These cover a good range of terms users would naturally use when seeking migration help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: Airflow 2.x to 3.x migration. The combination of 'Airflow', 'migration', '2.x to 3.x', and 'breaking changes' creates a clear, unique trigger profile that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong migration skill with excellent actionability and progressive disclosure. The workflow is well-sequenced with validation checkpoints, and the reference file structure is clean. Minor verbosity in the architecture section and some explanatory content that Claude doesn't need prevent a perfect conciseness score, but overall the skill is highly effective and well-organized.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some explanatory content Claude doesn't need (e.g., explaining what the DAG processor and Triggerer are, the architecture overview paragraph). The quick reference tables and code examples are well-targeted, but some sections could be tightened. | 2 / 3 |
Actionability | Provides fully executable code examples (Python client, REST API calls), specific Ruff commands with exact flags, concrete search patterns for problematic code, and detailed import/context mapping tables that are directly usable. | 3 / 3 |
Workflow Clarity | The 'Migration at a Glance' section provides a clear 5-step sequence with explicit validation (re-running Ruff after changes, manual search checklist). The workflow includes feedback loops (step 4: implement incrementally, re-run checks) and cautions about testing updated logic. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in the main file and well-signaled one-level-deep references to four specific reference files (config-changes.md, migration-patterns.md, removed-methods.md, migration-checklist.md). Quick reference tables provide immediate value without requiring navigation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- astronomer/agents
- Commit
166c98a
- Reviewed
Table of Contents
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.