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.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./astro-airflow-mcp/.claude/skills/airflow-adapter/SKILL.mdQuality
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 solid, focused skill description that clearly identifies its niche (Airflow API version compatibility) and provides explicit trigger guidance. The 'Use when' clause covers the main scenarios well. The description could be slightly improved by listing more concrete actions (e.g., creating adapters, wrapping API calls, handling deprecations).
Suggestions
Add more specific concrete actions like 'Creates adapter wrappers, handles deprecated API calls, maps v2 endpoints to v3 equivalents' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airflow adapter pattern, v2/v3 API compatibility) and some actions (version detection, adding new API methods), but doesn't list multiple concrete actions like specific adapter operations or code patterns. | 2 / 3 |
Completeness | Clearly answers both 'what' (Airflow adapter pattern for v2/v3 API compatibility) and 'when' (Use when working with adapters, version detection, or adding new API methods that need to work across Airflow 2.x and 3.x) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords a developer would use: 'Airflow', 'adapter', 'version detection', 'API compatibility', 'Airflow 2.x and 3.x', 'API methods'. These are terms developers would naturally mention when dealing with this problem. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Airflow version compatibility adapters across 2.x and 3.x. Unlikely to conflict with other skills due to the highly specific domain and version references. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is admirably concise and well-structured as an overview, but it falls short on its stated purpose of guiding work on adding new API methods across Airflow versions. The quick reference shows consumption of the adapter but not extension. The referenced supporting files could fill this gap but aren't available to verify.
Suggestions
Add a concrete workflow for adding a new adapter method: define in base.py, implement in v2 and v3 adapters, with specific code examples showing the pattern
Include a brief example showing how version-specific field/endpoint differences are handled when implementing a new method (e.g., different response schemas)
Show how to import/access `_get_adapter()` so the quick reference is copy-paste ready
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Airflow is or how adapters work conceptually. Every line provides actionable information—architecture diagram, file locations, and usage examples. | 3 / 3 |
Actionability | Provides a quick reference code snippet showing adapter usage, but it's incomplete—doesn't show how to import or access `_get_adapter()`, and doesn't cover adding new API methods (mentioned in the skill description). The guidance for the stated purpose of 'adding new API methods that need to work across Airflow 2.x and 3.x' is absent. | 2 / 3 |
Workflow Clarity | The architecture flow is clear and the auto-detection is mentioned, but there's no workflow for the key use case described: adding new adapter methods. No steps for implementing a new method across both adapters, no validation or testing guidance. | 2 / 3 |
Progressive Disclosure | References to @api-differences.md and @patterns.md are well-signaled and one level deep, which is good. However, no bundle files were provided to verify these references exist, and the content that should elaborate on adding new methods (the primary use case) isn't present in either the body or referenced files. | 2 / 3 |
Total | 9 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- astronomer/agents
- Commit
535a040
- 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.