multiAI Summary Pending
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.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/airflow-dag-patterns/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/sickn33/airflow-dag-patterns/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/airflow-dag-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How airflow-dag-patterns Compares
| Feature / Agent | airflow-dag-patterns | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.