CtrlK
BlogDocsLog inGet started
Tessl Logo

airflow-hitl

Use when the user needs human-in-the-loop workflows in Airflow (approval/reject, form input, or human-driven branching). Covers ApprovalOperator, HITLOperator, HITLBranchOperator, HITLEntryOperator, HITLTrigger. Requires Airflow 3.1+. Does not cover AI/LLM calls (see airflow-ai).

77

Quality

96%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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 skill that excels at actionability and conciseness. Its standout design choice is teaching Claude to discover current API signatures from the registry rather than hardcoding potentially stale parameter lists — a robust, future-proof approach. The workflow is clearly sequenced with an explicit safety checklist. The only minor weakness is that all content is inline with no bundle files for progressive disclosure, though the content length is reasonable for the complexity covered.

DimensionReasoningScore

Conciseness

The skill is lean and efficient throughout. It assumes Claude knows Python, Airflow concepts, and REST APIs. No unnecessary explanations of what HITL means or how deferrable operators work internally. Every section earns its place with actionable content.

3 / 3

Actionability

Provides fully executable code examples (the approval gate DAG is copy-paste ready), concrete CLI commands for registry discovery, and specific jq filters. The approach of discovering live signatures rather than hardcoding is itself a concrete, actionable methodology with exact commands provided.

3 / 3

Workflow Clarity

The 6-step sequence is clearly ordered and logically progressive: pick capability → discover signatures → write code → understand behavior → integrate externally → validate. Step 6 provides an explicit safety checklist with validation checkpoints, and the skill includes feedback loops (e.g., 'if the registry shows a param that this skill does not mention, prefer the registry').

3 / 3

Progressive Disclosure

The content is well-structured with clear sections and cross-references to related skills (airflow, airflow-ai, authoring-dags, testing-dags). However, there are no bundle files to offload detailed content to, and some sections like the behavior contracts and external integration patterns could potentially be split into separate reference files. The inline content is moderately long but not egregiously so.

2 / 3

Total

11

/

12

Passed

Description

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 clearly defines its scope, provides specific operator names and use cases, and explicitly delineates boundaries with related skills. The 'Use when...' clause is well-placed at the start, trigger terms are natural and comprehensive, and the exclusion note proactively prevents conflicts with the airflow-ai skill.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and components: approval/reject workflows, form input, human-driven branching, and names five specific operators/triggers (ApprovalOperator, HITLOperator, HITLBranchOperator, HITLEntryOperator, HITLTrigger).

3 / 3

Completeness

Explicitly answers both 'what' (human-in-the-loop workflows covering approval/reject, form input, branching with specific operators) and 'when' ('Use when the user needs human-in-the-loop workflows in Airflow'). Also includes version requirements and a clear exclusion boundary.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'human-in-the-loop', 'approval', 'reject', 'form input', 'branching', plus specific operator names. Also includes 'HITL' abbreviation and 'Airflow' context. The exclusion note ('not AI/LLM calls') further helps with routing.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche (HITL in Airflow 3.1+), specific operator names as triggers, and an explicit exclusion ('Does not cover AI/LLM calls, see airflow-ai') that directly addresses potential conflict with a related skill.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
astronomer/agents
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.