CtrlK
BlogDocsLog inGet started
Tessl Logo

airflow-adapter

Airflow adapter pattern for v2/v3 API compatibility. Use when working with adapters, version detection, or adding new API methods that need to work across Airflow 2.x and 3.x.

70

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

80%

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

A tight, action-oriented overview with concrete code, but it falls short on workflow clarity and progressive disclosure: there are no validation checkpoints and the two referenced files are missing from the bundle.

Suggestions

Add the missing reference files (e.g. references/api-differences.md and references/patterns.md) or remove the Related Files entries so signaled references resolve to real bundle paths.

For consequential operations like trigger_dag_run, add a short verification step (e.g. check the returned run_id / state) so the workflow has an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is a lean ~30-line overview with no padding and no explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

The Quick Reference gives concrete, executable usage of the adapter API (_get_adapter(), list_dags(limit=100), trigger_dag_run with a real conf dict) rather than pseudocode or abstract direction.

3 / 3

Workflow Clarity

An architecture flow is shown but there is no sequenced procedure with validation checkpoints, and consequential operations like trigger_dag_run have no verification guidance, capping this at 2.

2 / 3

Progressive Disclosure

Sections are well organized and references are signaled, but the referenced files (@api-differences.md, @patterns.md) do not exist in the bundle, so the navigation does not actually resolve.

2 / 3

Total

10

/

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, concise description that clearly communicates both purpose and trigger conditions with natural keywords and a distinctive niche. Its only weakness is specificity, naming just a couple of actions rather than a fuller enumeration.

DimensionReasoningScore

Specificity

Names the domain ('Airflow adapter pattern for v2/v3 API compatibility') and a couple of actions ('version detection', 'adding new API methods'), but does not enumerate a comprehensive set of concrete capabilities as the score-3 anchor requires.

2 / 3

Completeness

It explicitly states what it does and provides an explicit 'Use when...' trigger clause covering adapters, version detection, and cross-version API methods, satisfying both the what and the when.

3 / 3

Trigger Term Quality

Phrases like 'adapters', 'version detection', 'adding new API methods', and 'Airflow 2.x and 3.x' are natural terms a user would say when needing this skill, matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The Airflow v2/v3 adapter pattern is a clear niche with distinctive triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.