agentleFS
sp1esp1e/claude-skills/data-quality-audit/SKILL.md

data-quality-audit

Skill1 starsChanged 31 days agoMITView on GitHub

Comprehensive data quality assessment against business rules, schema constraints, and freshness expectations. Activate when validating data pipeline outputs before production use, auditing a dataset against defined business rules, or producing a quality scorecard for a data asset.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

When to use

  • A data pipeline has just loaded new data and needs validation before downstream reports consume it
  • A stakeholder has flagged data quality concerns (wrong totals, unexpected nulls, stale data)
  • You need to produce a formal data quality scorecard for a data asset as part of a data governance process
  • You are onboarding a new data source and need to understand its quality profile before building on it

Process

  1. Null and completeness audit — run scripts/null_counter.py for a column-by-column null profile. Flag columns above acceptable thresholds for the business context.
  2. Duplicate detection — run scripts/duplicate_finder.py to identify full-row and key-level duplicates. Determine if duplicates are intentional (versioning) or errors (pipeline fan-out).
  3. Referential integrity check — run scripts/referential_integrity.py to validate that foreign key values in child tables exist in parent tables. Report orphan rate per relationship.
  4. Value range validation — run scripts/value_range_validator.py with business rules defined in references/business_rule_patterns.md. Flag values outside acceptable ranges.
  5. Freshness check — run scripts/freshness_check.py to verify the dataset is up to date — compare the latest record timestamp against the expected lag for this pipeline.
  6. Score and classify findings — map each finding to a quality dimension using references/quality_dimensions.md. Assign severity (CRITICAL / HIGH / MEDIUM / LOW).
  7. Produce deliverables — fill assets/audit_report_template.html for a shareable report; fill assets/quality_rubric.md for a concise scorecard.

Inputs the skill needs

  • Required: dataset (CSV / Parquet / database table reference)
  • Required: schema relationships — which columns are primary keys, which are foreign keys to which tables
  • Required: business rules — acceptable value ranges, expected value sets, freshness SLA
  • Optional: acceptable error rates — at what threshold does a failure become CRITICAL vs. HIGH
  • Optional: pipeline schedule — to assess freshness relative to expected update frequency

Output

  • assets/audit_report_template.html (filled) — full quality report, shareable with stakeholders
  • assets/quality_rubric.md (filled) — one-page quality scorecard with dimension scores
  • Script console output — per-check pass/fail counts for each validation script

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.