validate-dqs

Validate Data Quality Specification documents for completeness and quality standards.

5|1|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill validate-dqs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-dqs
Source: https://github.com/RDEWAI/Redefining-DataEngineering-With-AI/tree/main/chapter-6/dq-engineer-plugin/skills/validate-dqs
Command: npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill validate-dqs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Data Quality Engineers often spend hours manually reviewing Data Quality Specifications (DQS) for missing sections, invalid rules, and missing traceability, leading to delayed handoffs and downstream pipeline errors. This Skill automates that validation process to catch issues early.

Core Features & Use Cases

  • Comprehensive DQS Validation: Checks all 9 required sections, metadata, field-level rules, referential integrity, statistical tests, reconciliation rules, alert frameworks, and traceability for completeness and quality.
  • Auto-Fix & Guided Resolution: Automatically fixes CRITICAL issues, prompts you to address WARNING-level gaps, and reports INFO-level suggestions for improvement.
  • Use Case: A data quality engineer validating a patient 360 DQS before handoff to the engineering team can use this Skill to ensure all bronze/silver/gold layer rules are present, FK checks are defined, and STM/DMS references are properly linked.

Quick Start

Use the validate-dqs skill to validate your Data Quality Specification file at 'outputs/dqs/patient-360.md' and get a ranked list of issues to fix.

Frequently Asked Questions about validate-dqs

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

FAQPage Schema
How do I validate a Data Quality Specification document for missing sections and traceability gaps?

To validate a DQS document, run an automated validation process that checks all required sections, field-level rules, and traceability links against quality standards. This generates a severity-ranked report identifying missing sections, invalid rules, and traceability gaps for immediate remediation.

What is a Data Quality Specification audit for medallion layer data pipelines?

A DQS audit for medallion data pipelines systematically reviews field-level validation rules, referential integrity checks, and reconciliation rules across bronze, silver, and gold layers. It ensures all metadata, alert frameworks, and traceability links meet engineering standards before pipeline implementation.

How do I check referential integrity and statistical distribution rules in my DQS file?

You validate referential integrity and statistical distribution rules in a DQS file by running an automated specification check against quality standards. The validation process scans for defined foreign key checks and statistical tests, flagging any missing or invalid rules as critical issues or warnings.

Can I automatically fix critical data quality specification issues during validation?

Yes, automated DQS validation can apply auto-fix capabilities to resolve CRITICAL severity issues immediately. It also generates user prompts to address WARNING-level gaps and provides INFO-level suggestions, tracking corrections to improve future specification quality.

Does DQS validation support alert and escalation framework checks for data engineering workflows?

Yes, DQS validation thoroughly checks alert and escalation frameworks within data engineering workflows. It validates the completeness of alert protocols in the specification to ensure proper monitoring and escalation paths are defined for downstream pipeline failures.

What are the limitations of automated rule audits for Data Quality Specifications?

Automated DQS rule audits are limited to evaluating structural completeness, rule validity, and traceability gaps within the specification document. They validate the design of field-level rules and alert frameworks but do not execute these rules against live medallion layer data.