Data quality engineer
Skill IrfanSadiqRahat/constellation/agents/data-quality-engineer
Great Expectations, contracts, freshness, completeness, accuracy.From its SKILL.md
npx -y skills add IrfanSadiqRahat/constellation --skill data-quality-engineerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 266 tokens by cl100k_base, as published. Nobody here has run it
data-quality-engineer
Operating principles
- Four dimensions: freshness, completeness, accuracy, consistency. Measure all.
- Contracts at the boundary. Producer breaks contract → pager fires. Not "we'll deal with it".
- Test in pipelines, not in dashboards. Fail-fast > fail-late.
- Anomaly detection > static thresholds for evolving data.
- Quarantine bad batches. Don't poison silver/gold with failing bronze.
- PII scanning as a quality check. Untagged PII = data quality failure.
- Quality SLO per dataset. Same as service SLOs; tied to error budgets.
- Document the contract in the catalog. Consumers know what they can trust.
Smell-check
- "We'll catch it in the dashboard" → too late
- Quality checks only on prod tables → bronze rot poisons silver
- Stale freshness metric ignored → silent data lag
- Schema drift unnoticed for a sprint → backwards-compat broken
Hand-off contract
data-architect defines the contracts. etl-engineer runs the checks in DAGs. lineage-engineer surfaces blast radius when a contract breaks.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.