des-persona-data-quality-engineer

Define data quality dimensions, thresholds, and alerting rules for data pipelines.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/DKSang/DES-SKILL --skill des-persona-data-quality-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: des-persona-data-quality-engineer
Source: https://github.com/DKSang/DES-SKILL/tree/main/skills/des-persona-data-quality-engineer
Command: npx skills add https://github.com/DKSang/DES-SKILL --skill des-persona-data-quality-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams define data quality in a way that is measurable, monitorable, and actionable during a data engineering lifecycle rather than leaving quality as vague documentation.

Core Features & Use Cases

  • Layer-aware data quality design: Selects DQ dimensions per layer (e.g., Bronze/Silver/Gold) with thresholds that reflect different baselines and expectations.
  • Operational orchestration & observability: Specifies how quality checks run, how failures are detected and surfaced, and what operational responses occur (alerts, retries, runbooks).
  • Governance-ready handling: Adds handoffs when DQ rules involve PII/retention concerns or when validation implies architecture/design changes.
  • Use Case: When onboarding a new ingestion pipeline, define completeness and validity thresholds with baseline windows, set retry/backoff behavior, and require an owner-backed remediation path before promoting to downstream layers.

Quick Start

Use the skill to define your data quality dimensions, thresholds with baseline windows, and the alerting and runbook response rules for a pipeline going from Bronze to Gold.

Frequently Asked Questions about des-persona-data-quality-engineer

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

FAQPage Schema
How do I enforce data quality expectations as actionable rules in data pipelines?

Enforce data quality expectations by converting them into measurable rules, operational signals, and response paths. This approach applies dimensions, thresholds, anomaly baselines, and orchestration behavior directly within your data pipelines.

What is the best way to set data quality thresholds across different data layers?

Set data quality thresholds using a layer-aware design for Bronze, Silver, and Gold layers. Baseline-aware thresholding ensures expectations reflect different baselines and specific requirements at each data layer.

How do I configure retry policies and alerts for data quality check failures?

Configure retry policies and alerts by specifying how data quality checks run and how failures are detected. Operational responses include alerts, backoff behavior, and runbooks to guide remediation during pipeline execution.

Why does my data pipeline require an owner-backed remediation path before releasing downstream?

Production-release gating requires an owner-backed remediation path to prevent unresolved validation failures from moving downstream. This governance-ready handling ensures accountability when DQ rules involve PII or architecture changes.

How do I implement data observability and governance for PII retention in data pipelines?

Implement data observability and governance by adding handoffs when DQ rules involve PII or retention concerns. This ensures explicit ownership and remediation paths are established for validation failures impacting sensitive data.

Can I use baseline-aware thresholding for anomaly detection during pipeline onboarding?

Use baseline-aware thresholding for anomaly detection by defining completeness and validity thresholds with baseline windows. This is essential when onboarding new ingestion pipelines to establish accurate operational signals.