data-quality-checker

Validate data quality across pipelines, schemas, and warehouses using six core dimensions.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill data-quality-checker-robotijn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-quality-checker
Source: https://github.com/robotijn/ctoc/tree/main/skills/data-ml/data-quality-checker
Command: npx skills add https://github.com/robotijn/ctoc --skill data-quality-checker-robotijn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Data pipelines, warehouses, and producer-consumer interfaces often emit malformed, late, missing, or drifting data that silently corrupts downstream dashboards, machine learning models, and customer-facing surfaces without explicit validation guardrails.

Core Features & Use Cases

  • Six-dimension validation: Checks data against accuracy, completeness, consistency, timeliness, validity, and uniqueness standards, with every check explicitly tied to its served dimension.
  • Data contract enforcement: Validates formal producer-consumer agreements (schema, freshness SLA, volume bounds, versioning) at ingestion to prevent silent schema breaks from upstream changes.
  • Production observability guidance: Provides scan methodology and tooling recommendations for monitoring freshness, volume, schema drift, and referential integrity across pipeline and warehouse layers. Use case: A data engineering team preparing for a product launch can use this skill to audit all customer-facing tables for missing schema validation, orphan foreign keys, and unmet freshness SLAs before go-live.

Quick Start

Use the data-quality-checker skill to audit the customer_events table for missing schema validation, freshness SLA breaches, and orphan foreign key records.

Frequently Asked Questions about data-quality-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate data quality across pipelines to prevent corrupted dashboards?

Data quality validation checks datasets against six core dimensions—accuracy, completeness, consistency, timeliness, validity, and uniqueness—to prevent corrupted data from reaching downstream dashboards and models. It enforces ingestion-time schema validation and freshness SLA monitoring.

How do I enforce data contracts for producer-consumer interfaces?

Data contract enforcement validates formal producer-consumer agreements—covering schema, freshness SLA, volume bounds, and versioning—at ingestion time. This prevents silent schema breaks caused by upstream changes from reaching downstream surfaces.

What is distribution drift tracking and when do I need it for machine learning workflows?

Distribution drift tracking monitors statistical changes in data over time to detect when input data deviates from expected patterns. It is needed for machine learning workflows to prevent model degradation caused by shifting data distributions.

Can I monitor referential integrity and orphan foreign keys in my data warehouse?

Yes, referential integrity checks identify orphan foreign key records and validate relationships across warehouse layers. This ensures consistency within your data warehouse and prevents broken joins in downstream analytics.

What's the best way to detect volume anomalies and freshness SLA breaches in data pipelines?

Production data observability provides scan methodology and tooling recommendations for monitoring volume anomalies and freshness SLA breaches across pipeline layers. It uses quarantine-based error handling to isolate corrupted data before it reaches customers.

Does shift-left validation work for schema validation before data ingestion?

Yes, shift-left validation applies schema checks at ingestion time to catch malformed or missing data early. This prevents invalid records from entering your warehouse and enforced data contracts stop silent schema breaks.