← ClaudeAtlas

soda-checkslisted

Use when warehouse data quality (Snowflake, BigQuery, Postgres, Redshift and others) should be checked with YAML-based SodaCL: writing checks, configuration.yml data sources, soda scan runs and CI gating on the exit code, with Soda Core or Soda Cloud.
testland/qa-skills · ★ 0 · Testing & QA · score 72
Install: claude install-skill testland/qa-skills
# soda-checks ## Overview SodaCL (Soda Checks Language) is a YAML-based domain-specific language for data reliability. A typical Soda project ships two YAML files - `configuration.yml` (data source connection) and `checks.yml` (assertions) - and runs them through the `soda scan` CLI ([sodacl-overview][1], [sodacl-quickstart][2]). [1]: https://docs.soda.io/soda-v3/soda-cl-overview.md [2]: https://docs.soda.io/soda-v3/soda-cl-overview/quick-start-sodacl.md This skill covers SodaCL authoring, scan configuration, running, and CI integration. Use it when you want **YAML-only assertions on warehouse tables** without writing Python (in contrast to Great Expectations, which is Python-first) or compiling a dbt project. ## When to use - The repo has `configuration.yml` + `checks.yml` (the canonical Soda filenames per [sodacl-quickstart][2]). - The user asks about `checks for <table>:`, `missing_count`, `duplicate_count`, `freshness`, or `invalid_count` - SodaCL check types per [sodacl-overview][1]. - A pipeline needs warehouse-side data quality with no programmatic glue: SQL warehouses (Snowflake, BigQuery, Postgres, Redshift) are first-class data sources. - A team uses Soda Cloud for cross-team observability of scan results. ## Authoring checks ### File shape `checks.yml` is a list of `checks for <dataset>:` blocks. Each block lists assertions in SodaCL syntax ([sodacl-overview][1]): ```yaml # checks.yml checks for orders: - row_count between 1 and 10000000 -