data-validation-data-quality-checks
Sub-skill of data-validation: Data Quality Checks (+3).
Best use case
data-validation-data-quality-checks is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of data-validation: Data Quality Checks (+3).
Teams using data-validation-data-quality-checks should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/data-quality-checks/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How data-validation-data-quality-checks Compares
| Feature / Agent | data-validation-data-quality-checks | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of data-validation: Data Quality Checks (+3).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Data Quality Checks (+3) ## Data Quality Checks - [ ] **Source verification**: Confirmed which tables/data sources were used. Are they the right ones for this question? - [ ] **Freshness**: Data is current enough for the analysis. Noted the "as of" date. - [ ] **Completeness**: No unexpected gaps in time series or missing segments. - [ ] **Null handling**: Checked null rates in key columns. Nulls are handled appropriately (excluded, imputed, or flagged). - [ ] **Deduplication**: Confirmed no double-counting from bad joins or duplicate source records. - [ ] **Filter verification**: All WHERE clauses and filters are correct. No unintended exclusions. ## Calculation Checks - [ ] **Aggregation logic**: GROUP BY includes all non-aggregated columns. Aggregation level matches the analysis grain. - [ ] **Denominator correctness**: Rate and percentage calculations use the right denominator. Denominators are non-zero. - [ ] **Date alignment**: Comparisons use the same time period length. Partial periods are excluded or noted. - [ ] **Join correctness**: JOIN types are appropriate (INNER vs LEFT). Many-to-many joins haven't inflated counts. - [ ] **Metric definitions**: Metrics match how stakeholders define them. Any deviations are noted. - [ ] **Subtotals sum**: Parts add up to the whole where expected. If they don't, explain why (e.g., overlap). ## Reasonableness Checks - [ ] **Magnitude**: Numbers are in a plausible range. Revenue isn't negative. Percentages are between 0-100%. - [ ] **Trend continuity**: No unexplained jumps or drops in time series. - [ ] **Cross-reference**: Key numbers match other known sources (dashboards, previous reports, finance data). - [ ] **Order of magnitude**: Total revenue is in the right ballpark. User counts match known figures. - [ ] **Edge cases**: What happens at the boundaries? Empty segments, zero-activity periods, new entities. ## Presentation Checks - [ ] **Chart accuracy**: Bar charts start at zero. Axes are labeled. Scales are consistent across panels. - [ ] **Number formatting**: Appropriate precision. Consistent currency/percentage formatting. Thousands separators where needed. - [ ] **Title clarity**: Titles state the insight, not just the metric. Date ranges are specified. - [ ] **Caveat transparency**: Known limitations and assumptions are stated explicitly. - [ ] **Reproducibility**: Someone else could recreate this analysis from the documentation provided.
Related Skills
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
worldenergydata-source-readiness
Route agents to the canonical worldenergydata source-readiness skill and summary script. Use when asked for worldenergydata data completeness, data locations, latest known data dates, scheduler freshness, source-readiness status, or acceptance-criteria inputs across the repo ecosystem.
sodir-data-extractor
Extract and process Norwegian Petroleum Directorate field and production data from SODIR
metocean-data-fetcher
Fetch real-time and historical metocean data from NDBC, CO-OPS, Open-Meteo, ERDDAP, and MET Norway. Use for buoy data retrieval, tidal observations, marine forecasts, and multi-source data fusion.
energy-data-visualizer
Interactive visualization for oil and gas production data analysis using Plotly dashboards
bsee-data-extractor
Extract and process BSEE (Bureau of Safety and Environmental Enforcement) data including production, WAR (Well Activity Reports), and APD (Application for Permit to Drill) data. Use for querying production data, well activities, drilling permits, completions, and workovers by API number, block, lease, or field with automatic data normalization and caching.
gtm-demo-validation-cache-regression-repair
Diagnose and repair GTM demo validation failures caused by legacy cache files missing intermediate chart data, especially in nested digitalmodel demo scripts using --from-cache.
worktree-pre-push-bypass-for-tier1-checks
Handle workspace-hub integration-branch pushes from isolated git worktrees when the pre-push hook incorrectly assumes sibling tier-1 repos exist under the worktree path.
tax-return-data-capture-and-archival
Capture structured tax return summaries as YAML for year-over-year comparison, with fallback to manual PDF download and relocation when automation fails
repo-separation-for-sensitive-data
Architecture pattern for splitting confidential data and reusable algorithms across repos
plan-gated-issue-validation-workflow
Systematic validation pattern for plan-approved GitHub issues with pre-existing deliverables
metadata-only-wiki-sweep-workflow
Disciplined inventory process for cataloging documents by filename/path without content claims, using parent-centric grouping to prevent stub proliferation