domains / data / data-quality-validation / data-quality-frameworks

data-quality-frameworks

Skill card

combined

The three copies share the same high-level scope (Great Expectations, dbt tests, data contracts) but diverge in how they instruct the agent. The foryourhealth111-pixel copy is a detailed, self-contained procedure with specific code patterns for Great Expectations suites and checkpoints. The rmyndharis and sickn33 copies are thin wrappers that delegate the actual work to an external file (resources/implementation-playbook.md) and add safety/limitation constraints not present in the first copy. Because the first copy contains the actual implementation steps while the others contain distinct safety and delegation constraints, crowning one would hide either the detailed patterns or the safety/delegation approach.

Repositories

Other copies

Combined skill

---
name: data-quality-frameworks
description: Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
---

# Data Quality Frameworks

Production patterns for implementing data quality with Great Expectations, dbt tests, and data contracts to ensure reliable data pipelines.

## When to Use This Skill

- Implementing data quality checks in pipelines
- Setting up Great Expectations validation
- Building comprehensive dbt test suites
- Establishing data contracts between teams
- Monitoring data quality metrics
- Automating data validation in CI/CD

## Do Not Use This Skill When

- The data sources are undefined or unavailable
- You cannot modify validation rules or schemas
- The task is unrelated to data quality or contracts

## Instructions

1. Identify critical datasets and quality dimensions (completeness, uniqueness, validity, accuracy, consistency, timeliness).
2. Define expectations/tests and contract rules.
3. Implement validation using Great Expectations suites and checkpoints, or dbt tests.
4. Automate validation in CI/CD and schedule checks.
5. Set alerting, ownership, and remediation steps.
6. If detailed patterns are required, open `resources/implementation-playbook.md`.

## Safety

- Avoid blocking critical pipelines without a fallback plan.
- Handle sensitive data securely in validation outputs.

## Limitations

- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

## Resources

- `resources/implementation-playbook.md` for detailed frameworks, templates, and examples.