Skip to main content

data-quality-frameworks

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.

설치로 이동

소스 정보

저장소
muhammedadnank/Antigravity-Skills
최근 소스 활동
2026년 6월 6일 18:30
감지된 SKILL.md 언어
영어
스타
13
포크
1

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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.
risk
unknown
source
community
date_added
2026-02-27
# Data Quality Frameworks Production patterns for implementing data quality with Great Expectations, dbt tests, and data contracts to ensure reliable data pipelines. ## Use this skill when - 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 - Identify critical datasets and quality dimensions. - Define expectations/tests and contract rules. - Automate validation in CI/CD and schedule checks. - Set alerting, ownership, and remediation steps. - 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. ## Resources - `resources/implementation-playbook.md` for detailed frameworks, templates, and examples. ## 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.
GitHub에서 보기