airflow-and-workflow-orchestration — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited airflow-and-workflow-orchestration (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when the problem is orchestration rather than transformation logic. It helps agents design Airflow, MWAA, Cloud Composer, Azure Data Factory, Step Functions, Google Cloud Workflows, or Databricks Workflows patterns with explicit dependencies, retries, ownership, backfills, and publish-safe cutover behavior.
Airflow DAGsDo not use this as a substitute for the underlying processing skill. Orchestration coordinates work; it does not define the compute logic itself.
Capture:
Decide whether the workload is:
Workflow tasks should call well-defined jobs, not hide business logic in orchestration code.
Account for:
Decide how catchup, reruns, and historical windows behave before enabling them.
A successful task chain is not enough if downstream tables fail quality checks.
AWS: prefer MWAA for dependency-rich DAGs, Step Functions for branching and service coordination, and lightweight event triggers for arrival-based flows.Azure: prefer Azure Data Factory or Synapse Pipelines for connector-heavy and parameterized workflows, and Databricks Workflows when execution stays in Databricks.GCP: prefer Cloud Composer for DAGs, Google Cloud Workflows for API and service coordination, and Cloud Scheduler plus Pub/Sub for simple triggers.Databricks: prefer Databricks Workflows or Delta Live Tables for platform-native jobs, and use an external orchestrator when dependencies cross platform boundaries.references/pipeline-orchestration-patterns.md when selecting or reviewing the orchestration model, not only the syntax of one tool.| Rationalization | Reality |
|---|---|
| "We can keep the transformation logic inside the DAG file." | That creates brittle orchestration code and harder testing and reuse. |
| "Retries are always safe." | Retries on non-idempotent tasks can duplicate data or corrupt publish layers. |
| "Catchup will handle backfills automatically." | Historical reprocessing usually needs different safeguards than normal schedule runs. |
| "The platform-default orchestrator is automatically the right one." | Tool choice should follow workload shape, cross-system boundaries, and recovery needs. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.