airflow-dag-patterns

Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.

1.01x

Quality

68%

Does it follow best practices?

Impact

96%

1.01x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/airflow-dag-patterns/SKILL.md

Quality

Content

50%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.

The body is concise and well-structured with useful use/do-not-use and safety sections, but the Instructions lack executable detail and the single referenced resource file is missing from the bundle, weakening both actionability and progressive disclosure.

Suggestions

Add a concrete minimal DAG code skeleton (e.g. with DAG() / @dag / @task and a schedule) so the Instructions are copy-paste executable instead of abstract directives.

Create the referenced `resources/implementation-playbook.md` (or remove/correct the reference) so progressive disclosure points to a real file.

Add an explicit validation feedback loop (e.g. run a DAG test / `dag.test()` in staging, fix on failure, re-run) to lift workflow clarity for batch operations.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge of Airflow without padding; the only redundancy is that `resources/implementation-playbook.md` is referenced twice (Instructions and Resources), a minor trim opportunity.	4 / 5
Actionability	The Instructions are abstract directives ("Identify data sources", "Design idempotent tasks", "Implement DAGs with observability") with no executable code, DAG skeleton, commands, or concrete examples — high-level hints missing the specific steps to execute.	2 / 5
Workflow Clarity	Four sequenced steps are listed and a "Validate in staging" step appears, but there is no validate→fix→retry feedback loop; for a batch-orchestration skill the missing explicit validation checkpoint caps this at 3.	3 / 5
Progressive Disclosure	Sections are well-organized and the reference is one level deep and clearly signaled, but the referenced `resources/implementation-playbook.md` does not exist in the bundle, so the disclosure path is broken.	3 / 5
	Total	12 / 20 Passed

Description

87%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.

The description is clear, third-person, and answers both what the skill does and when to use it with concrete trigger phrases. It is specific to the Airflow orchestration niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	"Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment" names the domain plus several concrete capability areas, though it stops short of enumerating the specific actions within each.	4 / 5
Completeness	It explicitly answers both "what" (build production Airflow DAGs with best practices for operators, sensors, testing, deployment) and "when" ("Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"creating data pipelines, orchestrating workflows, or scheduling batch jobs" are natural phrases users would say, with good coverage; a few common synonyms (e.g., ETL, job scheduling) are missing.	4 / 5
Distinctiveness Conflict Risk	"Apache Airflow DAGs" plus orchestration-specific triggers carve out a clear niche with minimal overlap risk against non-orchestration skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/airflow-dag-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.