SkillCoding & development
Trace a request through a codebase
Follow one request from entry point to storage or external boundary with concrete file references.
✳Claude Code
MIT · FreeView skill
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.
--- name: airflow-dag-patterns description: "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." risk: safe source: community date_added: "2026-02-27" --- # 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.--- name: airflow-dag-patterns description: "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." risk: safe source: community date_added: "2026-02-27" --- # 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.
Imported SKILL.md format for Claude Code, Codex and Cursor. Review the complete instructions and required tools before use. Package integrity checked; individual agent behavior has not been tested.