deploying-airflow

Deploys Airflow DAGs and projects. Use when deploying Airflow or answering anything about deployment - deploying DAGs/projects, pushing code, setting up CI/CD, deploying to production or deployment strategies for Airflow.

1.36x

Quality

74%

Does it follow best practices?

Impact

97%

1.36x

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/deploying-airflow/SKILL.md

Quality

Content

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

Highly actionable content with excellent copy-paste-ready commands and configs, weakened by redundancy (table plus repeating subsections, generic Docker basics) and the absence of post-deploy validation steps. Splitting the long compose/Helm configurations into reference files would improve both conciseness and progressive disclosure.

Suggestions

Add explicit validation checkpoints after each deploy path (e.g., verify `astro deploy` completed via the deploy queue, run `kubectl get pods -n airflow` and wait for Ready after `helm install`, and include rollback guidance via `helm rollback`), framing them as steps in the workflow rather than a passive command list.

Move the full `docker-compose.yaml` and `values.yaml` into reference files (e.g., `references/docker-compose-local.yaml`, `references/helm-values.yaml`) and keep only the key settings inline with pointers, reducing SKILL.md to a navigable overview.

Remove the duplication between the Deploy Commands table and the per-command subsections (keep one), and trim the generic Docker Compose operations Claude already knows to only the Airflow-specific invocations.

Dimension	Reasoning	Score
Conciseness	The Deploy Commands table is repeated almost verbatim by the four subsections that follow it, and "Common Operations" includes generic Docker Compose usage Claude already knows ("docker compose up -d", "docker compose logs -f"). Structure is mostly efficient, but these redundancies and the fully inlined 75-line compose file go beyond the "minor trimming" of a 4.	3 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: complete `astro deploy` variants, a complete working `docker-compose.yaml`, a full `values.yaml` with git-sync/resources, and `helm install/upgrade` and `kubectl` commands covering the common cases.	5 / 5
Workflow Clarity	Path selection is well sequenced ("Astro... For open-source, use Docker Compose for dev and the Helm chart for production"), but there are no validation checkpoints after any deploy. Deploys are batch operations affecting production, so per the rubric the absence of verification steps (e.g., check deploy status, confirm pods healthy, rollback guidance) caps this at 3.	3 / 5
Progressive Disclosure	Section headers are clear, but all three deployment paths are inlined monolithically — the 70–90-line `docker-compose.yaml` and `values.yaml` blocks clearly belong in separate reference files, and no bundle files exist. This fits anchor 3: structure present, but content that should be separate is inline.	3 / 5
	Total	14 / 20 Passed

Description

83%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 description with an explicit what-and-when structure and natural trigger terms. Minor improvements possible by naming the concrete deployment targets (Astro, Docker Compose, Kubernetes/Helm) to sharpen trigger matching and distinctiveness against related Astro skills.

Dimension	Reasoning	Score
Specificity	Lists several specific actions ("deploying DAGs/projects, pushing code, setting up CI/CD, deploying to production") beyond just naming the domain. Not a 5 because the actions are all deploy-variants and no specific platforms (Astro, Helm, Docker) are named.	4 / 5
Completeness	Explicitly answers both: "Deploys Airflow DAGs and projects" (what) and "Use when deploying Airflow or answering anything about deployment - deploying DAGs/projects, pushing code, setting up CI/CD..." (when), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases users would say are present ("deploying Airflow", "pushing code", "setting up CI/CD", "deploying to production"). A few natural synonyms and platform terms ("ship", "release", "Kubernetes", "Helm", "Astro") are missing, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	A clear Airflow-deployment niche with distinct triggers, though "answering anything about deployment" is slightly broad and sibling Astro skills (setting-up-astro-project, managing-astro-local-env) create minor overlap risk.	4 / 5
	Total	17 / 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: astronomer/agents
Path: skills/deploying-airflow/SKILL.md
Commit: 1ec1a1f

Reviewed: 24 hours 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.