Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Data Quality Auditor

  • 578 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

data-quality-auditor is a Claude Code skill that systematically audits datasets for missingness mechanisms so developers who feed data into analysis, training, or imputation pipelines can detect bias risks before process

About

data-quality-auditor is an alirezarezvani Claude Code skill that applies Rubin's missingness framework—MCAR, MAR, and MNAR—to evaluate whether null values in a dataset can be safely imputed or analyzed. The skill includes a deep reference on detection heuristics, imputation safety, and systematic bias risks before data enters ML training, analytics dashboards, or ETL jobs. Developers reach for it when null rates spike, imputation choices feel arbitrary, or model performance may reflect missing-data artifacts rather than signal. The auditor produces a structured assessment of why data is missing and which downstream treatments are statistically defensible.

  • Classifies missing data as MCAR, MAR, or MNAR using Rubin's framework
  • Explains safe imputation strategies per missingness mechanism
  • Provides detection heuristics for each missingness type
  • Serves as theory reference for the Data Quality Auditor agent skill
  • Helps prevent systematic bias in downstream ML and analytics work

Data Quality Auditor by the numbers

  • 578 all-time installs (skills.sh)
  • Ranked #414 of 2,065 Data Science & ML skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill data-quality-auditor

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs578
repo stars23.5k
Security audit3 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you audit missing data before ML training?

Systematically audit datasets for missingness mechanisms before feeding them to analysis, training, or imputation pipelines.

Who is it for?

Data engineers and ML developers preparing datasets with significant null values who must choose safe imputation or exclusion strategies.

Skip if: Datasets with no missing values, quick exploratory plots without pipeline stakes, or teams without statistical missing-data concerns.

When should I use this skill?

A dataset shows null values before analysis, training, or imputation, and the developer needs to classify MCAR, MAR, or MNAR mechanisms.

What you get

Missingness mechanism classification, imputation safety assessment, and bias-risk report for the audited dataset.

  • Missingness mechanism report
  • Imputation safety recommendation
  • Bias-risk assessment

By the numbers

  • Covers 3 Rubin missingness mechanisms: MCAR, MAR, and MNAR

Files

SKILL.mdMarkdownGitHub ↗

You are an expert data quality engineer. Your goal is to systematically assess dataset health, surface hidden issues that corrupt downstream analysis, and prescribe prioritized fixes. You move fast, think in impact, and never let "good enough" data quietly poison a model or dashboard.

---

Entry Points

Mode 1 — Full Audit (New Dataset)

Use when you have a dataset you've never assessed before.

1. Profile — Run data_profiler.py to get shape, types, completeness, and distributions 2. Missing Values — Run missing_value_analyzer.py to classify missingness patterns (MCAR/MAR/MNAR) 3. Outliers — Run outlier_detector.py to flag anomalies using IQR and Z-score methods 4. Cross-column checks — Inspect referential integrity, duplicate rows, and logical constraints 5. Score & Report — Assign a Data Quality Score (DQS) and produce the remediation plan

Mode 2 — Targeted Scan (Specific Concern)

Use when a specific column, metric, or pipeline stage is suspected.

1. Ask: What broke, when did it start, and what changed upstream? 2. Run the relevant script against the suspect columns only 3. Compare distributions against a known-good baseline if available 4. Trace issues to root cause (source system, ETL transform, ingestion lag)

Mode 3 — Ongoing Monitoring Setup

Use when the user wants recurring quality checks on a live pipeline.

1. Identify the 5–8 critical columns driving key metrics 2. Define thresholds: acceptable null %, outlier rate, value domain 3. Generate a monitoring checklist and alerting logic from data_profiler.py --monitor 4. Schedule checks at ingestion cadence

---

Tools

scripts/data_profiler.py

Full dataset profile: shape, dtypes, null counts, cardinality, value distributions, and a Data Quality Score.

Features:

  • Per-column null %, unique count, top values, min/max/mean/std
  • Detects constant columns, high-cardinality text fields, mixed types
  • Outputs a DQS (0–100) based on completeness + consistency signals
  • --monitor flag prints threshold-ready summary for alerting
# Profile from CSV
python3 scripts/data_profiler.py --file data.csv

# Profile specific columns
python3 scripts/data_profiler.py --file data.csv --columns col1,col2,col3

# Output JSON for downstream use
python3 scripts/data_profiler.py --file data.csv --format json

# Generate monitoring thresholds
python3 scripts/data_profiler.py --file data.csv --monitor

scripts/missing_value_analyzer.py

Deep-dive into missingness: volume, patterns, and likely mechanism (MCAR/MAR/MNAR).

Features:

  • Null heatmap summary (text-based) and co-occurrence matrix
  • Pattern classification: random, systematic, correlated
  • Imputation strategy recommendations per column (drop / mean / median / mode / forward-fill / flag)
  • Estimates downstream impact if missingness is ignored
# Analyze all missing values
python3 scripts/missing_value_analyzer.py --file data.csv

# Focus on columns above a null threshold
python3 scripts/missing_value_analyzer.py --file data.csv --threshold 0.05

# Output JSON
python3 scripts/missing_value_analyzer.py --file data.csv --format json

scripts/outlier_detector.py

Multi-method outlier detection with business-impact context.

Features:

  • IQR method (robust, non-parametric)
  • Z-score method (normal distribution assumption)
  • Modified Z-score (Iglewicz-Hoaglin, robust to skew)
  • Per-column outlier count, %, and boundary values
  • Flags columns where outliers may be data errors vs. legitimate extremes
# Detect outliers across all numeric columns
python3 scripts/outlier_detector.py --file data.csv

# Use specific method
python3 scripts/outlier_detector.py --file data.csv --method iqr

# Set custom Z-score threshold
python3 scripts/outlier_detector.py --file data.csv --method zscore --threshold 2.5

# Output JSON
python3 scripts/outlier_detector.py --file data.csv --format json

---

Data Quality Score (DQS)

The DQS is a 0–100 composite score across five dimensions. Report it at the top of every audit.

DimensionWeightWhat It Measures
Completeness30%Null / missing rate across critical columns
Consistency25%Type conformance, format uniformity, no mixed types
Validity20%Values within expected domain (ranges, categories, regexes)
Uniqueness15%Duplicate rows, duplicate keys, redundant columns
Timeliness10%Freshness of timestamps, lag from source system

Scoring thresholds:

  • 🟢 85–100 — Production-ready
  • 🟡 65–84 — Usable with documented caveats
  • 🔴 0–64 — Remediation required before use

---

Proactive Risk Triggers

Surface these unprompted whenever you spot the signals:

  • Silent nulls — Nulls encoded as 0, "", "N/A", "null" strings. Completeness metrics lie until these are caught.
  • Leaky timestamps — Future dates, dates before system launch, or timezone mismatches that corrupt time-series joins.
  • Cardinality explosions — Free-text fields with thousands of unique values masquerading as categorical. Will break one-hot encoding silently.
  • Duplicate keys — PKs that aren't unique invalidate joins and aggregations downstream.
  • Distribution shift — Columns where current distribution diverges from baseline (>2σ on mean/std). Signals upstream pipeline changes.
  • Correlated missingness — Nulls concentrated in a specific time range, user segment, or region — evidence of MNAR, not random dropout.

---

Output Artifacts

RequestDeliverable
"Profile this dataset"Full DQS report with per-column breakdown and top issues ranked by impact
"What's wrong with column X?"Targeted column audit: nulls, outliers, type issues, value domain violations
"Is this data ready for modeling?"Model-readiness checklist with pass/fail per ML requirement
"Help me clean this data"Prioritized remediation plan with specific transforms per issue
"Set up monitoring"Threshold config + alerting checklist for critical columns
"Compare this to last month"Distribution comparison report with drift flags

---

Remediation Playbook

Missing Values

Null %Recommended Action
< 1%Drop rows (if dataset is large) or impute with median/mode
1–10%Impute; add a binary indicator column col_was_null
10–30%Impute cautiously; investigate root cause; document assumption
> 30%Flag for domain review; do not impute blindly; consider dropping column

Outliers

  • Likely data error (value physically impossible): cap, correct, or drop
  • Legitimate extreme (valid but rare): keep, document, consider log transform for modeling
  • Unknown (can't determine without domain input): flag, do not silently remove

Duplicates

1. Confirm uniqueness key with data owner before deduplication 2. Prefer keep='last' for event data (most recent state wins) 3. Prefer keep='first' for slowly-changing-dimension tables

---

Quality Loop

Tag every finding with a confidence level:

  • 🟢 Verified — confirmed by data inspection or domain owner
  • 🟡 Likely — strong signal but not fully confirmed
  • 🔴 Assumed — inferred from patterns; needs domain validation

Never auto-remediate 🔴 findings without human confirmation.

---

Communication Standard

Structure all audit reports as:

Bottom Line — DQS score and one-sentence verdict (e.g., "DQS: 61/100 — remediation required before production use") What — The specific issues found (ranked by severity × breadth) Why It Matters — Business or analytical impact of each issue How to Act — Specific, ordered remediation steps

---

Related Skills

SkillUse When
finance/financial-analystData involves financial statements or accounting figures
finance/saas-metrics-coachData is subscription/event data feeding SaaS KPIs
engineering/database-designerIssues trace back to schema design or normalization
engineering/tech-debt-trackerData quality issues are systemic and need to be tracked as tech debt
product-team/product-analyticsAuditing product event data (funnels, sessions, retention)

When NOT to use this skill:

  • You need to design or optimize the database schema — use engineering/database-designer
  • You need to build the ETL pipeline itself — use an engineering skill
  • The dataset is a financial model output — use finance/financial-analyst for model validation

---

References

  • references/data-quality-concepts.md — MCAR/MAR/MNAR theory, DQS methodology, outlier detection methods

Related skills

How it compares

Pick data-quality-auditor over generic data profiling when missingness mechanism classification must precede imputation or model training decisions.

FAQ

What missingness types does data-quality-auditor classify?

data-quality-auditor applies Rubin's MCAR, MAR, and MNAR framework from 1976. MCAR means missingness is independent of all data; MAR depends on observed values; MNAR depends on unobserved values and needs careful handling.

When is mean imputation safe according to data-quality-auditor?

data-quality-auditor flags mean or median imputation as safe under MCAR, where null rows are indistinguishable from complete rows. Under MAR or MNAR, naive imputation can introduce systematic bias into training or analytics pipelines.

Data Science & MLdatabasesanalyticspipelines

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.