Skip to main content
ClaudeWave
Skill40.5k repo starsupdated today

airflow-dag-patterns

This skill provides production-ready patterns for building Apache Airflow DAGs, covering design principles, operators, sensors, testing, and deployment strategies. Use it when creating data pipeline orchestration, designing DAG structures with dependencies, implementing custom operators or sensors, testing locally, setting up production environments, or debugging failed runs.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/sickn33/antigravity-awesome-skills /tmp/airflow-dag-patterns && cp -r /tmp/airflow-dag-patterns/plugins/antigravity-awesome-skills-claude/skills/airflow-dag-patterns ~/.claude/skills/airflow-dag-patterns
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Apache Airflow DAG Patterns

Production-ready patterns for Apache Airflow including DAG design, operators, sensors, testing, and deployment strategies.

## Use this skill when

- Creating data pipeline orchestration with Airflow
- Designing DAG structures and dependencies
- Implementing custom operators and sensors
- Testing Airflow DAGs locally
- Setting up Airflow in production
- Debugging failed DAG runs

## Do not use this skill when

- You only need a simple cron job or shell script
- Airflow is not part of the tooling stack
- The task is unrelated to workflow orchestration

## Instructions

1. Identify data sources, schedules, and dependencies.
2. Design idempotent tasks with clear ownership and retries.
3. Implement DAGs with observability and alerting hooks.
4. Validate in staging and document operational runbooks.

Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.

## Safety

- Avoid changing production DAG schedules without approval.
- Test backfills and retries carefully to prevent data duplication.

## Resources

- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.