CtrlK
BlogDocsLog inGet started
Tessl Logo

airflow-new-sdk

Guide for implementing a brand-new language SDK for Airflow (AIP-108). Use this skill when a contributor wants to add support for a new programming language — designing the Python coordinator, implementing the wire protocol in the target language, writing the bundle format, and structuring the PR. Trigger on phrases like "new language SDK", "new SDK", "add support for [language]", "implement coordinator for", "SubprocessCoordinator", "BaseCoordinator", "new runtime", "AFBNDL01", "supervisor schema", or anything about bringing a new language into the Airflow executor ecosystem.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A well-structured, token-efficient skill body that relies on an authoritative external doc for bulk detail and supplies concrete file paths, a decision tree, and a PR checklist. It is held back only slightly by the absence of an explicit validation/retry feedback loop.

Suggestions

Add an explicit validate-then-fix feedback loop for the E2E test run (e.g., 'if wait_for_dag_run reports failure, inspect the SDK --logs channel and re-trigger before re-running pytest').

Consider a minimal executable coordinator skeleton for the SubprocessCoordinator path (the _build_execute_task_command method) so the most common case is copy-paste ready rather than file-layout only.

Make the E2E test assertions a short numbered checklist mirroring the PR checklist style, so the verification steps read as explicit checkpoints.

DimensionReasoningScore

Conciseness

Lean and efficient: it explicitly defers bulk detail to the authoritative 30_new_language_sdk.rst ('rather than reproducing it here', 'Read that section before writing any code') and assumes Claude's competence, with every section earning its place.

5 / 5

Actionability

Provides concrete file paths, a copy-paste test command, a base-class decision tree, and a numbered PR checklist; the only gap is that coordinator code is shown as file layout rather than executable code, which is justified by deferral to the rst reference.

4 / 5

Workflow Clarity

A sequenced PR checklist and a decision-tree checkpoint for base-class selection give a clear sequence; it falls short of 5 only because there is no explicit validate→fix→retry feedback loop for the E2E/PR operations.

4 / 5

Progressive Disclosure

Clear overview that defers detail one level deep to 30_new_language_sdk.rst, with an organized reference table of specific files to study; no bundle files exist, so references are well-signaled repo paths appropriately split from the skill body.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 precise, well-constructed description that fully answers what the skill does and when to use it, with multiple concrete actions and natural trigger phrases. It is highly distinctive and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'designing the Python coordinator', 'implementing the wire protocol in the target language', 'writing the bundle format', and 'structuring the PR' — giving comprehensive coverage of the skill's scope.

5 / 5

Completeness

Explicitly answers both 'what' (a guide for implementing a brand-new language SDK, with the four sub-tasks enumerated) and 'when' via an explicit 'Use this skill when...' clause plus concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides extensive natural trigger phrases a contributor would actually say ('new language SDK', 'new SDK', 'add support for [language]', 'implement coordinator for') plus technical identifiers (SubprocessCoordinator, AFBNDL01), covering synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (a new language SDK for Airflow AIP-108) with distinct, domain-specific triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

20

/

20

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
apache/airflow
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.