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.
85
81%
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 solid, well-targeted skill description for a niche domain. It clearly states both what the skill does and when to use it, with good trigger terms that developers working with Airflow version compatibility would naturally use. The only minor weakness is that the specific capabilities could be slightly more detailed (e.g., mentioning specific adapter operations or patterns).
| 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 in detail—e.g., it doesn't specify what kinds of adapters or what specific operations are performed. | 2 / 3 |
Completeness | Clearly answers both 'what' (Airflow adapter pattern for v2/v3 API compatibility) and 'when' (explicit 'Use when working with adapters, version detection, or adding new API methods that need to work across Airflow 2.x and 3.x'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords a developer would use: 'Airflow', 'adapter', 'v2/v3', 'API compatibility', 'version detection', 'Airflow 2.x and 3.x'. These are terms a user working in this domain would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche—Airflow v2/v3 adapter compatibility is a very distinct domain. Unlikely to conflict with other skills unless there are multiple Airflow-related skills, and even then the adapter/version-compatibility focus is clear. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise overview skill that effectively serves as a navigation hub for the adapter pattern. Its main weakness is that it lacks actionable guidance for the stated use case of adding new API methods that work across Airflow versions—there are no concrete steps or examples for extending the adapter. The quick reference shows consumption but not contribution.
Suggestions
Add a brief workflow (3-5 steps) showing how to add a new adapter method: define in base.py, implement in v2/v3 adapters, handle field differences, and test both versions.
Include a concrete example of implementing a new method (e.g., a stub showing the abstract method and one version-specific implementation) to make the 'adding new API methods' use case actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. Every line serves a purpose—architecture diagram, file locations, references, and a quick usage example. No unnecessary explanation of what Airflow is or how adapters work conceptually. | 3 / 3 |
Actionability | The quick reference shows concrete usage examples, but they are incomplete—there's no guidance on how to add a new adapter method, how version detection works internally, or what to do when extending the pattern. The description says 'Use when adding new API methods' but no steps for that are provided. | 2 / 3 |
Workflow Clarity | The architecture flow is clear and the auto-detection is mentioned, but there's no workflow for the stated use case of adding new API methods across versions. No steps for extending the adapter, no validation or testing guidance for ensuring both versions work. | 2 / 3 |
Progressive Disclosure | Clean overview with well-signaled one-level-deep references to api-differences.md and patterns.md. Key files are listed clearly. Content is appropriately split between this overview and the referenced files. | 3 / 3 |
Total | 10 / 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
0642adb
- 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.