Skip to content
Skills Library
Data & analytics · Review & audit

data-quality-gate

/data-quality-gate

Design validation checks for structured datasets and data pipelines. Use when ingesting, transforming, joining, exporting, or versioning data used by software or machine-learning systems.

Licence
MIT
Last repository change
30.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Design validation checks for structured datasets and data pipelines. Use when ingesting, transforming, joining, exporting, or versioning data used by software or machine-learning systems.

Original author description

Design validation checks for structured datasets and data pipelines. Use when ingesting, transforming, joining, exporting, or versioning data used by software or machine-learning systems.

How it works

  1. Procedure
  2. Deliverable
  3. Boundaries
Original SKILL.md headings · 20 lines, 208 words
SKILL.md preview
---
name: data-quality-gate
description: Design validation checks for structured datasets and data pipelines. Use when ingesting, transforming, joining, exporting, or versioning data used by software or machine-learning systems.
license: MIT
---

# Data Quality Gate

## Procedure
1. Define the intended use, data owner, source, allowable uses, sensitivity class, and expected freshness. Do not assume data is safe to use merely because it is accessible.
2. Write down the schema: field names, types, requiredness, allowed ranges, units, identifiers, timezone conventions, and null semantics.
3. Profile representative samples for missingness, duplicates, outliers, inconsistent categories, encoding problems, invalid dates, and suspicious distribution shifts.
4. Validate joins and identifiers. Check row counts before and after transformations to detect accidental fan-out or dropped records.
5. Define hard failures versus warnings. Make thresholds explicit and explain why they matter to downstream decisions.
6. Preserve lineage: source snapshot, transformation version, timestamps, and deterministic parameters. Avoid recording secrets or personal records in logs.
7. Run validation on a sample first, then on the intended dataset. Save a compact machine-readable summary and meaningful failure examples.

## Deliverable
Include schema contract, validation checks, counts, examples of failed rows with sensitive values redacted, and the go/no-go decision.

## Boundaries
- Do not silently impute, delete, or rewrite data to make validation pass.
- Never upload sensitive datasets to external services without authorization and a valid data-use basis.
- Label synthetic or inferred data; never represent it as collected fact.

Versions

RepositoryScoreLicence
This page · voyager67/AgentFieldkit100MIT
testland/qa100MIT

Database snapshot: 13.11.2026 · package version c5c5305bc9bb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100data-quality-checker
    Implement data quality checks, validation rules, and monitoring. Use when ensuring data quality, validating data pipelines, or implementing data governance.
  • 90clean-validate
    Design a data validation pipeline — schema checks, range validation, and quality metrics. Use when asked to "validate incoming data", "add schema checks", or "define data quality metrics".
  • 100data-pipeline-architect
    Analyzes and designs batch and streaming data pipelines with contracts, lineage, reliability, and cost controls. Use for ingestion and transformation systems. NOT for ad-hoc analysis or schema design.
  • 100data-quality-checker
    Validate data quality checker operations. Auto-activating skill for Data Pipelines. Triggers on: data quality checker, data quality checker Part of the Data Pipelines skill category. Use when working with data quality checker functionality. Trigger with phrases like "data…
  • 100fai-build-etl-pipeline
    Design ETL/ELT pipelines for AI data ingestion — extraction, transformation, quality checks, scheduling, and idempotent loads. Use this skill when building a data pipeline, ingesting documents for RAG, or fixing data-quality issues — even if the user only says "get this data into the system".
  • 100data-quality-audit
    Use when ingesting unfamiliar datasets, designing metrics or investigating data anomalies. Verify dataset integrity, semantic meaning and reproducibility before analysis or modeling. Do not use when a confirmed clean single scalar with no transformations.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.