data-checks
/data-checks
Rules for check-first data analysis - what a good check is, where checkpoints go, and the anti-patterns. Use when writing or reviewing checks, assertions or tests for data pipelines, analyses or models.
- Author
- steffen74 ↗
- Repository
- agentic-data-science ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Rules for check-first data analysis - what a good check is, where checkpoints go, and the anti-patterns. Use when writing or reviewing checks, assertions or tests for data pipelines, analyses or models.
Original author description
Rules for check-first data analysis - what a good check is, where checkpoints go, and the anti-patterns. Use when writing or reviewing checks, assertions or tests for data pipelines, analyses or models.
How it works
- What a good check is
- Checkpoints
- Rules of the loop
- Anti-patterns
- Implementation
SKILL.md preview
--- name: data-checks description: Rules for check-first data analysis - what a good check is, where checkpoints go, and the anti-patterns. Use when writing or reviewing checks, assertions or tests for data pipelines, analyses or models. --- # Data checks Analysis code rarely fails loudly. A **check** is an automated assertion that must hold before a result counts. Checks replace reading every line of generated code: they make correctness observable. ## What a good check is A good check compares the pipeline’s state with an **independent source of truth**: something the pipeline did not compute. | Source of truth | Example check | |---|---| | The raw file | Row count after loading equals the line count of the source file | | A key definition | Exactly one row per date and product after every merge | | A calendar | Every date of the period present once; no dates outside it | | A submission template | Prediction IDs equal the template’s IDs, same order, no missing values | | The split definition | Latest training date is earlier than the earliest validation date | | Domain bounds | Temperature between −30 and 45 °C; sales non-negative | | A known result | Baseline metric on validation equals the value recorded when it was first computed | ## Checkpoints Checks live at **checkpoints**, the boundaries between pipeline stages: 1. **Load**: shape, columns, types, row count vs. source. 2. **Merge**: row count unchanged (for left joins), keys unique, match rate as expected. 3. **Features**: no feature uses information beyond the leakage boundary; no unexpected missing values introduced. 4. **Split**: disjoint, ordered by time or group as planned, sizes as expected. 5. **Predictions**: IDs and count match, no missing values, values in plausible range. 6. **Metrics**: computed on the intended data; baseline reproduces. Agree the checkpoints with the user before writing checks. Not every checkpoint needs every check; the critical paths do. ## Rules of the loop - **Red before green.** Write the check, see it fail for the right reason (or pass on a state you know is correct), then rely on it. - **One checkpoint at a time.** Add checks where you are working, not everywhere at once. - **Fix the data, not the check.** A failing check is changed only with the user’s agreement and a logged reason. - **Keep the surprises.** Every bug found by hand becomes a permanent check. ## Anti-patterns - **Tautological**: the expected value is computed the same way as the result (`assert len(df) == len(df)`, a mean compared with itself). It passes by construction. - **Loosened to pass**: tolerances widened or conditions removed until green. - **Output-only**: only the final metric is checked, so an upstream error that happens to help the metric survives. - **Test-set peeking**: any decision taken while looking at test results. ## Implementation Prefer `pytest` tests under `checks/` that load the pipeline’s intermediate outputs, run with one command. In notebook-only projects, an `assert` cell at each checkpoint with a clear message is the fallback.
Versions
The database has no other skills named data-checks.
Database snapshot: 13.11.2026 · package version b637c02a4ae1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100data-quality-checker
Implement data quality checks, validation rules, and monitoring. Use when ensuring data quality, validating data pipelines, or implementing data governance. - 100data-pipeline-quality
Automated data quality checks for pipelines. Testing pyramids, dbt test patterns, data contracts, circuit breakers, and monitoring. Use when implementing data quality checks, writing dbt tests, defining data contracts, setting up pipeline validation, building automated quality… - 100test-generator
Generates dbt tests including schema tests, data quality tests, and freshness checks. Use when adding tests to dbt models or implementing data quality validation. - 90data
Pipelines, warehouses, dbt models and metrics, where failure is silently wrong numbers rather than a crash. Use when "the dashboard is wrong", "the numbers do not match", "add data quality checks", "safe backfill", or an upstream schema change broke a join. Covers freshness,… - 90data-quality-checks
Layer freshness, volume, schema, and distribution checks with quarantine and alert discipline. Use when adding quality gates to pipelines or when consumers keep finding bad data first. - 100data-catalog-updater
Process data catalog updater operations. Auto-activating skill for Data Pipelines. Triggers on: data catalog updater, data catalog updater Part of the Data Pipelines skill category. Use when working with data catalog updater functionality. Trigger with phrases like "data catalog…