CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

88

1.36x
Quality

Does it follow best practices?

Impact

97%

1.36x

Average score across 3 eval scenarios

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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 complete, executable commands and configs across Astro, Docker Compose, and Kubernetes. It is held back by verbosity, absent deploy-validation/rollback checkpoints for production deploys, and a monolithic structure that inlines large configs instead of offloading them to reference files.

Suggestions

Add validation/verification checkpoints to each deploy path — e.g., after `astro deploy` check the deploy queue/success, and after Helm install run `kubectl rollout status` or a smoke test — plus a brief rollback step.

Move the large docker-compose.yaml and values.yaml blocks into reference files (e.g., references/docker-compose.yaml, references/values.yaml) and signal them from the body to improve progressive disclosure and reduce inline tokens.

Trim concept re-explanation such as the service-purpose table and restated command descriptions; assume Claude knows Airflow's basic architecture and let each command's effect stand on its own.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands, but includes unnecessary explanation Claude already knows (a service-purpose table, 'This is recommended for learning', restating what each command does) and could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands and complete config blocks — `astro deploy` variants, a full docker-compose.yaml, a real values.yaml, and kubectl commands.

3 / 3

Workflow Clarity

A top-level path-selection guide and sequenced CI/CD patterns are present, but for a risky production-deployment skill there are no validation checkpoints or rollback/verify feedback loops, capping this dimension at 2.

2 / 3

Progressive Disclosure

No bundle files exist and the single ~435-line file inlines large config blocks (docker-compose.yaml, values.yaml) for three platforms that could be split into separate reference files with signaled navigation.

2 / 3

Total

9

/

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.

A strong, third-person description with concrete actions, an explicit 'Use when' trigger clause covering natural phrasings, and a well-bounded Airflow-deployment niche. It cleanly satisfies all four dimensions without fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Deploys Airflow DAGs and projects', 'pushing code', 'setting up CI/CD', 'deploying to production', 'deployment strategies' — matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers what ('Deploys Airflow DAGs and projects') and when via a clear 'Use when...' clause enumerating multiple deployment scenarios.

3 / 3

Trigger Term Quality

Covers natural terms users would say — 'deploying Airflow', 'deployment', 'deploying DAGs/projects', 'pushing code', 'CI/CD', 'deploying to production' — with good variation.

3 / 3

Distinctiveness Conflict Risk

A clear Airflow-deployment niche with distinct triggers; unlikely to conflict with the related authoring/testing/astro-setup skills it references.

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.

Validation16 / 16 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.