orchestration-and-backfills — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited orchestration-and-backfills (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.
Reliable data systems are shaped as much by rerun behavior as by transformation logic. This skill ensures schedules, retries, and backfills are deliberate, safe, and reversible.
Specify:
Historical reprocessing should not silently behave like daily incremental runs unless that has been proven safe. For /backfill or publish-bound replay, load safe-backfill-and-replay-orchestration first and complete templates/backfill-plan.yaml before execution.
Include:
Backfills can overload warehouses, queues, clusters, or downstream consumers.
Use a dry run, limited slice, or non-production environment when possible.
| Rationalization | Reality |
|---|---|
| "The scheduler will handle retries for us." | Default retries may duplicate writes or hide real data issues. |
| "Backfill is just rerunning the job for older dates." | Historical loads often need different concurrency, checks, and cutover rules. |
| "We can figure out rollback during the incident." | Recovery plans created during outage pressure are usually incomplete. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.