data-quality

data-quality is a skill for Claude Code from ChrisGVE/localdata-mcp. It costs 30 tokens per session (655 once invoked), scanned A, original, Apache-2.0.

A data-checking workflow that examines whether a dataset is complete, consistent, valid, and free of unexpected duplicates.

In plain words
What is it for?
Use it to inspect databases or data files, review tables and columns, measure missing values, and identify possible duplicate or unique identifier fields.
Why use it?
It helps you find missing, conflicting, invalid, or repeated data before relying on it for analysis.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the localdata-mcp plugin — 18 skills, 11 agents, 1 MCP server shipped together

Good fit Use it to inspect databases or data files, review tables and columns, measure missing values, and identify possible duplicate or unique identifier fields.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chrisgve/localdata-mcp/data-quality
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ChrisGVE/localdata-mcp --skill data-quality
Clone the repo
git clone --depth 1 https://github.com/ChrisGVE/localdata-mcp

Made for: Claude Code.

Or install localdata-mcp, the plugin that ships this one along with the rest of its 18 skills, 11 agents, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for data-quality

README.md
[![agentmods](https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/data-quality/github.svg)](https://agentmods.dev/skills/chrisgve/localdata-mcp/data-quality)
Your own site
<a href="https://agentmods.dev/skills/chrisgve/localdata-mcp/data-quality"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/data-quality/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for data-quality

Your own site · 80×15
<a href="https://agentmods.dev/skills/chrisgve/localdata-mcp/data-quality"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/data-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 655 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00655
Opus 5 $0.00015 $0.00328
Sonnet 5 $0.00006 $0.00131
Haiku 4.5 $0.00003 $0.00065

Measured 9d ago against content hash cfca1600383d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

data-quality scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/exploration/data-quality/SKILL.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Data Quality Assessment

Perform a comprehensive data quality audit covering completeness, consistency, validity, and uniqueness.

Steps

  1. Connect if needed. If $ARGUMENTS is a file path, call connect_database to load it. If it is a database name, proceed directly. Call describe_database to list all tables and row counts.

  2. Profile each table. For each table (or the primary tables if many), call describe_table to get column types, nullability, and cardinality. Call get_data_quality_report for detailed quality metrics.

  3. Assess completeness. Call execute_query to compute null percentages per column. Classify:

    • Complete (< 1% null): no action needed
    • Minor gaps (1-10% null): note but likely manageable
    • Significant gaps (10-30% null): flag for imputation or exclusion decisions
    • Severe gaps (> 30% null): column may be unusable without careful treatment
  4. Check uniqueness. For each column, call execute_query to compare distinct count against total count. Identify:

    • Candidate keys (100% unique)
    • High-cardinality categoricals (many unique values but not keys)
    • Suspicious duplicates (IDs that should be unique but are not)
  5. Validate value ranges. Call execute_query to compute min, max, mean, and percentiles for numeric columns. Flag:

    • Impossible values (negative ages, future dates in historical data, percentages > 100)
    • Extreme outliers (values beyond 3 IQR from quartiles)
    • Suspicious constants (columns with a single value)
  6. Check consistency. Look for:

    • Mixed data types within columns (numbers stored as strings)
    • Inconsistent formats (date formats, case sensitivity, encoding)
    • Referential integrity (foreign keys with no matching parent)
    • Contradictory records (same entity with conflicting attribute values)
  7. Report findings. Present a structured quality scorecard:

    • Overall data health score (percentage of columns with no issues)
    • Per-column quality summary: completeness, uniqueness, validity
    • Ranked list of issues from most to least severe
    • Impact assessment: which issues would affect which types of analysis
    • Remediation suggestions for each issue category

Read the full file on GitHub · 51 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 51 lines · 30 tokens per session scan A cfca1600383d

Subscribe to this mod's changes

data-quality is a skill published in the GitHub repository ChrisGVE/localdata-mcp (4 stars, last pushed 26d ago), licensed Apache-2.0. It adds 30 tokens to every session and 655 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

wingman-mcp

Add persistent, interactive task plan management to your agent. Wingman tracks plans and tasks across a long conversation — Claude creates plans, ticks tasks after completing work, and a live panel renders inline in the chat. Install the MCP server first, then use these tools to manage plans and tasks throughout any…

adeoluwaadesina/wingman-mcp · 68 tokens

liveagent-code-review

Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.

Stack-Cairn/LiveAgent · 54 tokens

skills-creator

Create or update LiveAgent runtime skills. Use when you need to summarize a workflow into a skill, write it into the fixed user skills root, validate it, package it, or refine a skill's references for LiveAgent's SkillsManager flow.

Stack-Cairn/LiveAgent · 53 tokens

skills-installer

Install, list enabled, validate, or package LiveAgent skills. Use when you need to inspect the skills enabled in the current conversation, import a local skill directory or package, search/install from ClawHub, install from a GitHub repo/tree URL, or reconcile conflicts during an upgrade.

Stack-Cairn/LiveAgent · 62 tokens

triaging-incidents

Creating, triaging, updating, and analyzing ServiceNow incidents. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM operations, SLA breaches…

jschuller/mcp-server-servicenow · 82 tokens

reviewing-update-sets

Reviewing, analyzing, and comparing ServiceNow update sets before promotion. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, "what changed in this update set," or…

jschuller/mcp-server-servicenow · 77 tokens