← ClaudeAtlas

data-quality-conventionslisted

Use when designing data-quality coverage for a new data product or auditing an existing one: choosing dbt tests vs Great Expectations vs Soda, column vs table-level checks, severity tiers, SLA and freshness conventions, and anti-patterns to avoid.
testland/qa-skills · ★ 0 · Testing & QA · score 72
Install: claude install-skill testland/qa-skills
# data-quality-conventions A reference catalog for **how** to design data-quality coverage. Pairs with the engine-specific skills (`dbt-testing`, `great-expectations`, `soda-checks`) - those tell you the **how** of running checks; this tells you **which** checks and **where**. ## Engine selection Use this matrix to pick an engine before authoring any checks. Mixing engines is fine in a large platform - the `data-quality-gate` skill exists precisely to reconcile their outputs. | Use case | Preferred engine | Why | |-------------------------------------------------------|------------------|-----| | Repo is a dbt project; assertions live next to models | dbt-tests | Tests run as part of `dbt build`, share the project's adapter, and live in the same `schema.yml` as the column docs. | | Python ELT, programmatic suite generation, runtime data connectors | Great Expectations | First-class Pandas / SQL / Spark batches; suites composable in Python. | | YAML-only checks against a SQL warehouse, cross-team observability via Soda Cloud | Soda | SodaCL is a focused DSL; no Python or dbt required. | | Mix of warehouse + non-warehouse sources | dbt + GX or Soda + GX | Use dbt or Soda for warehouse coverage; GX for non-warehouse (file uploads, Spark jobs, ad-hoc Pandas). | | Brand-new project, no preference | dbt-tests if you already have dbt; otherwise Soda for YAML simplicity | Lowest co