data-quality-frameworks
Build Reliable Data Quality Frameworks
Unreliable data pipelines create incorrect reports, failed models, and costly investigations. This skill designs practical checks, contracts, alerts, and validation workflows.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "data-quality-frameworks" from https://skillstore.io/skills/sickn33-data-quality-frameworks.md and its manifest at https://skillstore.io/api/skills/sickn33-data-quality-frameworks/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "data-quality-frameworks". Create quality checks for an orders model with order, customer, amount, status, and creation fields.
Expected outcome:
- Order identifiers must be present and unique.
- Customer identifiers must be present and match the customer model.
- Amounts must be positive and remain within an approved business range.
- Statuses must use the approved lifecycle values.
- Creation timestamps must be valid, recent, and not in the future.
Using "data-quality-frameworks". Outline a production rollout for daily warehouse validation.
Expected outcome:
- Start with warning-only checks on critical datasets.
- Measure failure rates and adjust thresholds with dataset owners.
- Route alerts to named owners with clear remediation steps.
- Block pipelines only for stable critical checks with fallback procedures.
- Review quality metrics and contract changes on a scheduled basis.
Using "data-quality-frameworks". Draft the scope for an orders data contract.
Expected outcome:
- Identify the producer, consumers, owner, and support contact.
- Define field types, required values, keys, privacy classifications, and compatibility rules.
- Set freshness, availability, and latency objectives.
- Document quality checks, change notices, and migration responsibilities.
Security Audit
Medium RiskAll 16 static alerts are false positives caused by Markdown references, schema fields, SQL identifiers, and ordinary safety guidance. One medium-risk semantic issue remains because an example report includes raw observed values and can print them to pipeline logs.
Confirmed security concerns (1)
Risk Factors
โ๏ธ External commands (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-data-quality-frameworks/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-data-quality-frameworks?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-data-quality-frameworks?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-data-quality-frameworks/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-data-quality-frameworks.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
sickn33. (2026). data-quality-frameworks security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-data-quality-frameworks/audits/5BibTeX citation
@techreport{sickn33-sickn33-data-quality-frameworks-2026,
author = {sickn33},
title = {data-quality-frameworks security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-data-quality-frameworks/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "data-quality-frameworks security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-data-quality-frameworks/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-data-quality-frameworks:audit:5"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
wshobson-data-quality-frameworks
2026-08-21
sickn33-data-quality-frameworks
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Protect Analytics Pipelines
Add focused dbt tests for keys, accepted values, relationships, freshness, and row counts.
Standardize Platform Validation
Create reusable Great Expectations suites, checkpoints, alerts, and failure policies across warehouse datasets.
Define Producer Contracts
Document schemas, ownership, privacy classifications, quality rules, and service levels for shared data products.
Try These Prompts
Create a data quality plan for [dataset]. Include completeness, uniqueness, validity, and freshness checks for these columns: [columns].
Design dbt tests for [model] using this schema: [schema]. Include key, relationship, range, accepted-value, freshness, and row-count tests.
Design a Great Expectations workflow for [datasets]. Define suites, checkpoints, schedules, alerts, owners, redaction rules, and nonblocking fallback behavior.
Create a versioned contract and rollout plan for [data product]. Cover schema compatibility, privacy, quality metrics, service levels, CI gates, and migration.
Best Practices
- Prioritize critical datasets and columns before expanding validation coverage.
- Version contracts and review thresholds with producers, consumers, and dataset owners.
- Redact sensitive values from validation results, alerts, reports, and pipeline logs.
Avoid
- Do not block production pipelines with uncalibrated checks or missing fallback procedures.
- Do not hardcode thresholds without measuring normal behavior and documenting ownership.
- Do not expose raw sensitive records when reporting failed validations.
Frequently Asked Questions
Which frameworks does this skill cover?
Can it generate checks for an existing schema?
Does it run validation against my warehouse?
How should failed checks affect pipelines?
Can it help define data contracts?
How should sensitive data be handled?
Developer Details
Author
sickn33License
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/data-quality-frameworksRef
f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
Maintenance freshness
7/26/2026
Usage
7 downloads ยท 108 views
File structure