community-automations/data-quality-watch

Research & Intel

PublicClaude subagent

Data Quality Watch

Broken pipelines stay silent until someone notices a dashboard looks wrong, usually days later. This watcher catches the break when it happens.

sonnet4 daysdbtPostgresGreat ExpectationsSlack
ClaudeClaude
ROI for
README.md

Why this subagent

Broken pipelines stay silent until someone notices a dashboard looks wrong, usually days later. This watcher catches the break when it happens.

It profiles each table on a schedule for freshness, row counts, and schema, then compares against the last known-good run. A drop, a stale load, or a changed column triggers a Slack alert to the owning team, naming the table, the failed check, and the last value that looked right.

How it runs

    • Read

      Used at step 01 to kick off the pipeline.

    • Write

      Used at step 01 to kick off the pipeline.

    • WebFetch

      Used at step 01 to kick off the pipeline.

    • WebSearch

      Used at step 01 to kick off the pipeline.

Sample output

json
// Sample output
// (generated when the pipeline finishes)

On a schedule, check tracked tables for freshness, row counts, and schema drift, and alert owners on any deviation.

Unlock the rest

The full agent definition, install snippet, and starter task are gated for community members.

Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.