Build Airflow 3.1+ plugins that embed FastAPI apps, custom UI pages, React components, middleware, macros, and operator links directly into the Airflow UI. Use this skill whenever the user wants to create an Airflow plugin, add a custom UI page or nav entry to Airflow, build FastAPI-backed endpoints inside Airflow, serve static assets from a plugin, embed a React app in the Airflow UI, add middleware to the Airflow API server, create custom operator extra links, or call the Airflow REST API from inside a plugin. Also trigger when the user mentions AirflowPlugin, fastapi_apps, external_views, react_apps, plugin registration, or embedding a web app in Airflow 3.1+. If someone is building anything custom inside Airflow 3.1+ that involves Python and a browser-facing interface, this skill almost certainly applies.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that thoroughly covers specific capabilities, provides abundant natural trigger terms, explicitly states both what the skill does and when to use it, and occupies a clearly distinct niche. The description is comprehensive without being padded—every clause adds meaningful selection criteria. The only minor concern is that it's somewhat long, but the length is justified by the breadth of specific triggers included.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: build plugins embedding FastAPI apps, custom UI pages, React components, middleware, macros, and operator links. Very detailed enumeration of capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (build Airflow 3.1+ plugins with FastAPI apps, UI pages, React components, etc.) and 'when' with explicit 'Use this skill whenever...' and 'Also trigger when...' clauses providing comprehensive trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Airflow plugin', 'custom UI page', 'FastAPI', 'React app', 'operator extra links', 'AirflowPlugin', 'fastapi_apps', 'external_views', 'react_apps', 'Airflow REST API', 'Airflow 3.1+'. Covers both natural language and technical class names. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Airflow 3.1+ plugin development specifically for UI/web-facing features. The version specificity (3.1+), the specific class names (AirflowPlugin, fastapi_apps), and the narrow domain make conflicts with other skills very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, highly actionable skill that provides comprehensive, executable guidance for building Airflow 3.1+ plugins. Its greatest strengths are the complete code examples, clear step-by-step workflow, pre-flight checklist, and excellent pitfalls table. The main weakness is its length — at 400+ lines it could benefit from splitting detailed reference material (JWT management, API patterns, component types) into separate files to improve token efficiency and progressive disclosure.
Suggestions
Extract the JWT token management section and common API endpoint patterns (Step 4-5) into a separate AIRFLOW_API.md reference file, keeping only a brief summary and link in the main skill.
Move the 'Other plugin component types' section (Step 6: macros, middleware, operator links, React apps) into a separate COMPONENTS.md file, since these are independent reference topics that not every plugin needs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive and mostly efficient, but includes some sections that could be tightened — for example, the JWT token management block is quite long, the 'Alternative: Direct database access' warning is verbose, and some explanatory comments within code could be trimmed. However, it avoids explaining basic concepts Claude already knows (FastAPI, Python, etc.) and most content earns its place. | 2 / 3 |
Actionability | Excellent actionability throughout — every section provides fully executable, copy-paste-ready code with correct imports, concrete endpoint patterns, specific file structures, and real CLI commands. The code examples are complete and production-ready, not pseudocode. | 3 / 3 |
Workflow Clarity | The skill follows a clear numbered step sequence (Steps 1-7) with explicit validation checkpoints ('Before writing any code, verify' checklist), a pitfalls table for error recovery, and clear guidance on when to skip steps (e.g., 'skip to Step 5 or Step 6'). The pre-flight checklist and common pitfalls table serve as effective validation mechanisms. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical progression, but it's a long monolithic document (~400+ lines) that could benefit from splitting detailed sections (JWT management, API endpoint patterns, component types) into separate reference files. The external references at the bottom are good, but inline content like the full SDK call patterns and streaming proxy could live in linked files. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (592 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
166c98a
Table of Contents
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.