CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A highly actionable body with concrete commands, code, and mapping tables, and a clear migration sequence. Weaknesses are explanatory prose that could be trimmed, missing explicit validation checkpoints in the workflow, and broken/missing reference files.

Suggestions

Tighten the Architecture & Metadata DB Access prose into bullet-pointed facts so it reads as reference rather than explanation.

Add an explicit validation checkpoint to the workflow (e.g., 'After each change, re-run Ruff and the checklist; only proceed when no AIR issues remain') to turn the implicit loop into a validate→fix→retry gate.

Create the four referenced files (config-changes.md, migration-patterns.md, removed-methods.md, migration-checklist.md) under references/ and fix the body's 'reference/' links to match, so the progressive-disclosure pointers resolve to real content.

DimensionReasoningScore

Conciseness

Mostly efficient with dense tables, code, and concrete commands, but the Architecture section and several prose gotchas explain component roles and behavior in a way that could be tightened; not every token earns its place.

2 / 3

Actionability

Provides fully executable Ruff commands, complete runnable code examples (ListDagsOperator, REST API call), concrete import/context mapping tables, and specific env-var settings — copy-paste ready.

3 / 3

Workflow Clarity

The 'Migration at a Glance' gives a clear 5-step sequence with a re-run-Ruff loop, but it lacks explicit validate→fix→retry checkpoints; for a batch code-modification operation the scoring notes cap this at 2.

2 / 3

Progressive Disclosure

A well-signaled one-level-deep 'Reference Files' section points to four files, but none of those files exist on disk and the path 'reference/' does not match the bundle's 'references/' convention, so the offload is broken rather than genuinely progressive.

2 / 3

Total

9

/

12

Passed

Description

90%

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, well-structured description with explicit 'Use when' triggers, natural keywords, and a distinct niche. The main weakness is second-person voice in the instruction clause and a mildly over-claiming 'Always load this skill as the first step' directive.

Suggestions

Rewrite the instruction clause in third person to avoid the second-person 'you' (e.g., 'When Airflow 2.x code needing migration is detected, prompt the user to confirm before upgrading').

Soften the over-claim 'Always load this skill as the first step for any migration-related request' to reflect genuine triggering conditions rather than self-promotion.

DimensionReasoningScore

Specificity

Names concrete actions ('migrating Apache Airflow 2.x projects to Airflow 3.x', 'detect Airflow 2.x code that needs migration', 'prompt the user and ask'), but uses second-person voice ('If you detect...', 'ask if they want you to help upgrade'), which per the guidelines reduces the specificity score by one.

2 / 3

Completeness

Explicitly states what it does ('Guide for migrating Apache Airflow 2.x projects to Airflow 3.x') and when to use it via a clear 'Use when the user mentions...' trigger clause, satisfying both what and when.

3 / 3

Trigger Term Quality

Covers natural terms users would say — 'Airflow 3 migration, upgrade, compatibility issues, breaking changes, modernize their Airflow codebase' — matching the top anchor's coverage of natural phrasing.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Airflow 2-to-3 migration) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 5 missing

Warning

Total

14

/

16

Passed

Repository
astronomer/agents
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.