analyze-data-quality

Assesses dataset trustworthiness for analysis, modeling, dashboards, experiments, or downstream pipelines.

1|2|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/MuzeWinter/CooperAPI-Plugin --skill analyze-data-quality-muzewinter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-data-quality
Source: https://github.com/MuzeWinter/CooperAPI-Plugin/tree/main/plugins/data-analytics/skills/analyze-data-quality
Command: npx skills add https://github.com/MuzeWinter/CooperAPI-Plugin --skill analyze-data-quality-muzewinter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this Skill to determine whether a dataset is trustworthy enough for analysis, modeling, dashboards, experiments, or downstream pipelines, and to spot the issues that can quietly corrupt decisions.

Core Features & Use Cases

  • Quality Profiling: Review grain, keys, row counts, nulls, duplicates, and schema shape before trusting the data.
  • Risk-Focused Checks: Evaluate completeness, uniqueness, validity, consistency, integrity, timeliness, volume, and drift against the dataset’s intended use.
  • Analytical Impact: Identify problems like broken joins, late backfills, leakage, stale partitions, or distribution shifts that can bias reports and models.

Quick Start

Ask the Skill to assess the attached table, file, or dataframe for quality risks before you use it in analysis or reporting.

Frequently Asked Questions about analyze-data-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check data quality before using a dataframe for analysis?

You can assess data quality by applying compact profiling to check grain, keys, nulls, duplicates, and schema shape, ensuring your dataframe or table is trustworthy enough for analysis, modeling, or dashboards.

What is schema drift and how does it impact data pipelines?

Schema drift happens when the data structure changes unexpectedly. Identifying schema drift is a key data quality profiling step that prevents broken downstream pipelines, corrupted dashboards, and invalid model training.

Can I detect distribution shift and broken joins in query results?

Yes, you can evaluate query results for broken joins, referential integrity, and distribution shifts. These risk-focused checks identify analytical impacts like leakage, late backfills, or stale partitions that can bias reports and models.

Does this data profiling approach work for tables, files, and dataframes?

Yes, this data profiling approach works directly with tables, query results, files, and dataframes. It assesses completeness, uniqueness, validity, and timeliness against the dataset's intended analytical use.

How do I test for freshness and duplicates in a dataset?

You test for dataset freshness and duplicates by running quality profiling checks. This evaluates timeliness and uniqueness to catch stale partitions or duplicate rows before they corrupt downstream pipelines or modeling.

What is the best way to find data leakage and backfill issues?

The best way to find data leakage and late backfill issues is to run temporal and segment analysis on your dataset. This identifies distribution shifts and analytical risks that can quietly bias experiments and models.