analytics-with-claude-code: Skill for Claude Code

.claude/skills/data-quality/SKILL.md

data-quality is a skill for Claude Code from adityawrk/analytics-with-claude-code. It costs 65 tokens per session (3,217 once invoked), scanned A, original, MIT.

A data-checking workflow that evaluates a dataset across completeness, uniqueness, consistency, timeliness, accuracy, and validity. It produces a scorecard for those six areas.

In plain words
What is it for?
Use it to audit a CSV, Parquet file, database table, or DataFrame, especially when onboarding a new data source or checking pipeline output.
Why use it?
It helps reveal missing values, duplicates, invalid records, stale data, and other problems before data is used in reports or pipelines. It also records basic information such as row count and column count.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is adityawrk/analytics-with-claude-code's own configuration. It tells Claude Code how to work on analytics-with-claude-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything analytics-with-claude-code configures →

Reuse

Borrowing it

Nothing to install: this file belongs to adityawrk/analytics-with-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/adityawrk/analytics-with-claude-code/main/.claude/skills/data-quality/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/adityawrk/analytics-with-claude-code

Made for: Claude Code.

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/adityawrk/analytics-with-claude-code/data-quality/github.svg)](https://agentmods.dev/skills/adityawrk/analytics-with-claude-code/data-quality)
Your own site
<a href="https://agentmods.dev/skills/adityawrk/analytics-with-claude-code/data-quality"><img src="https://agentmods.dev/badge/skills/adityawrk/analytics-with-claude-code/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/adityawrk/analytics-with-claude-code/data-quality"><img src="https://agentmods.dev/badge/skills/adityawrk/analytics-with-claude-code/data-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,217 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.00065 $0.03217
Opus 5.5 $0.00026 $0.01287
Sonnet 5.5 $0.00013 $0.00643
Haiku 4.5 $0.00006 $0.00322

Measured 2mo ago against content hash 4ed2e97235b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.claude/skills/data-quality/SKILL.md · 363 lines

How it starts

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

Data Quality Checker

You are a data quality engineer performing a rigorous assessment. You will evaluate data across six dimensions, score each one, and produce a data quality scorecard. Follow every section below.

Step 0: Environment Setup

import pandas as pd
import numpy as np
from datetime import datetime, timedelta
import hashlib
import re
import warnings
warnings.filterwarnings('ignore')

pd.set_option('display.max_columns', None)
pd.set_option('display.float_format', lambda x: f'{x:.4f}')

Step 1: Data Ingestion and Context

  1. Load the data (CSV, Parquet, database table, or DataFrame).
  2. Ask the user or infer from context:
    • What is this dataset? (e.g., user events, transactions, product catalog)
    • What is the grain? (one row = one what?)
    • What is the expected primary key? (if not obvious, attempt to detect it)
    • What is the expected refresh frequency? (real-time, hourly, daily, weekly)
    • Are there known constraints? (e.g., amount > 0, status IN ('active','inactive'), end_date >= start_date)
  3. Record the metadata: row count, column count, file size/memory usage, load timestamp.

Step 2: Completeness Assessment

Completeness measures the extent to which expected data is present.

2.1 Column-Level Completeness

For every column, compute:

completeness = pd.DataFrame({
    'column': df.columns,
    'null_count': df.isnull().sum().values,
    'null_pct': (df.isnull().sum() / len(df) * 100).round(2).values,
    'empty_string_count': [(df[col] == '').sum() if df[col].dtype == 'object' else 0 for col in df.columns],
    'disguised_null_count': [
        df[col].isin(['N/A', 'n/a', 'NA', 'null', 'NULL', 'None', 'none', '-', '--', 'unknown', 'UNKNOWN', 'TBD', 'tbd']).sum()
        if df[col].dtype == 'object' else 0
        for col in df.columns
    ]
})
completeness['total_missing'] = completeness['null_count'] + completeness['empty_string_count'] + completeness['disguised_null_count']
completeness['effective_null_pct'] = (completeness['total_missing'] / len(df) * 100).round(2)

Read the full file on GitHub · 363 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. 2mo ago First seen · 363 lines · 65 tokens per session scan A 4ed2e97235b6

Subscribe to this mod's changes

data-quality is a skill published in the GitHub repository adityawrk/analytics-with-claude-code (6 stars, last pushed 8mo ago), licensed MIT. It adds 65 tokens to every session and 3,217 once invoked, about $0.0003 per session on Opus 5.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

snowflake-dbt-model-refactoring

Refactor a bloated dbt model on Snowflake safely and produce a quantified before/after report that explains which qualities improved and why — not just raw deltas. Extends the standard refactor flow with (1) downstream impact analysis via dbt-analyze, (2) row-count + column-hash parity validation via data-parity, (3)…

AltimateAI/data-engineering-skills · 195 tokens

optimizing-databricks-sql

Analyze DBSQL queries, including SQL embedded in notebooks (spark.sql(...), %sql cells), for anti-patterns, lint issues, and performance problems, using Databricks-specific dialect and platform knowledge (Delta, Photon, Unity Catalog) layered on top of altimate-code's generic SQL engine. Use when a user asks to…

AltimateAI/data-engineering-skills · 98 tokens

mssql-to-snowflake-dbt-migration

Convert MS SQL Server source code (stored procs, views, T-SQL scripts) into dbt models targeting Snowflake, with build-first-then-parity, isolated-schema deployment, and a migration dashboard. Use when: (1) User says "migrate this T-SQL to dbt on Snowflake", "convert these stored procs end-to-end", "move from SQL…

AltimateAI/data-engineering-skills · 240 tokens

end-to-end-snowflake-pipeline

Build an end-to-end Snowflake pipeline — ticket → dbt models + orchestration DAG → PR → self-review → ticket comment. Use when: (1) User says "build a pipeline for X end-to-end", "create an end-to-end flow", "set up the pipeline per JIRA-123" (2) Scope spans dbt models AND orchestration AND a PR — not just one of them…

AltimateAI/data-engineering-skills · 221 tokens

snowflake-query-optimization

End-to-end Snowflake query optimization — fetch, rewrite, prove parity, benchmark, report. Use when: (1) User wants an end-to-end flow (fetch + rewrite + parity + benchmark + report), not just a rewrite (2) Input is a .sql file path in the repo (optionally :L10-L80 line range), OR a Snowflake queryid (UUID) (3) User…

AltimateAI/data-engineering-skills · 221 tokens

dbt-model-enhancement

Scoped enhancement of ONE existing dbt model from a ticket, with a validated PR as the deliverable. Use when: (1) User says "update per JIRA-123", "add column X to this model", "enhance based on this ticket" (2) Task is a scoped change to a specific existing model — one model, one ticket, one PR (3) User expects dbt…

AltimateAI/data-engineering-skills · 198 tokens