CtrlK
BlogDocsLog inGet started
Tessl Logo

airflow-testing-to-orchestra

Use this skill when an Airflow DAG contains data quality or testing operators: SqlCheckOperator, SQLThresholdCheckOperator, GreatExpectationsOperator, SodaCheckOperator, DbtTestOperator, or any custom SQL assertion task. Triggers: any task with sql= parameter used for validation, any use of Great Expectations or Soda, any dbt test step.

70

Quality

86%

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 highly actionable, well-organized migration reference dominated by concrete before/after code and a useful Gotchas section. It is slightly held back by repeated YAML boilerplate and the absence of an explicit validation feedback loop.

Suggestions

Add a short validation step to the workflow, e.g. 'after writing the YAML, confirm threshold expressions against Orchestra's /pipelines/schema validator before committing', to give an explicit validate-then-retry loop.

Factor the repeated connection/depends_on/condition/tags YAML keys into a noted shared snippet or a small reference file so each operator example shows only the differing parameters.

Trim the Overview's definitional sentence about what each Airflow operator is, since Claude already knows these operators.

DimensionReasoningScore

Conciseness

The body is dense with executable YAML/Python and a comparison table, assuming Claude's competence, but repeats YAML boilerplate (connection, depends_on) across examples and includes a light overview explanation that could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready Airflow→Orchestra before/after pairs for every operator family (SqlCheck, SQLThresholdCheck, DbtTest, GreatExpectations, Soda, schema validation, non-blocking tests, alerts), covering the common cases fully.

5 / 5

Workflow Clarity

The before/after structure gives a clear mapping flow and the Gotchas section supplies checkpoints (single-number requirement, threshold syntax, semantics inversion), but there is no explicit validate-then-retry feedback loop in the workflow itself.

4 / 5

Progressive Disclosure

The single file is well-sectioned with clear headers and one-level-deep external doc links, and no bundle files exist to mis-reference; it is not a 5 only because ~350 lines of operator examples all live inline where a reference file split could help.

4 / 5

Total

17

/

20

Passed

Description

91%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 strong, specific description with excellent trigger term coverage and a clear niche. Its only weakness is that the 'what' (convert these operators to Orchestra test jobs) is implied rather than explicitly verb-stated.

Suggestions

State the action explicitly, e.g. 'Converts Airflow data quality/testing operators into Orchestra test jobs' before the 'Use when...' clause, so the 'what' is as explicit as the 'when'.

DimensionReasoningScore

Specificity

The description enumerates concrete operator types (SqlCheckOperator, SQLThresholdCheckOperator, GreatExpectationsOperator, SodaCheckOperator, DbtTestOperator, custom SQL assertion) plus concrete trigger conditions, giving comprehensive specific coverage rather than vague language.

5 / 5

Completeness

The 'when' is exceptionally explicit (a 'Use this skill when...' clause plus a dedicated 'Triggers:' list), but the 'what' is only implied by the enumerated operator list rather than stating the conversion action (mapping to Orchestra test jobs).

4 / 5

Trigger Term Quality

It includes natural terms an Airflow user would actually say — 'Great Expectations', 'Soda', 'dbt test', 'data quality', 'testing operators', and 'sql= parameter' — covering the relevant synonyms and framings.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche — Airflow data quality/testing operators — with distinct, specific triggers, so it is unlikely to fire for the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
orchestra-hq/orchestra-skills
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.