data-quality-audit
Skill3 starsChanged 32 days agoMITView on GitHub
Run this audit BEFORE any modeling conversation gets serious. Work through the phases; report findings as a table at the end. Print dtypes and challenge them: - Numeric columns loaded as object (commas, currency symbols, whitespace) - IDs and zip codes as integers (leading zeros destroyed) - Dates as strings with mixed formats in one column - Booleans as 0/1/2 Fix dtype issues before computing anything else; null-rate statistics lie otherwise. For every column with any nulls: - Null rate…
8 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Suryanandx/qvac-uitheir own version, first seen Nov 1, 2026
- GentleZeal/DirtyData-Killertheir own version, first seen Nov 1, 2026
- Nomanriaz786/claude-consulting-teamtheir own version, first seen Nov 1, 2026
- yuiseki/GeoAI-master-skillstheir own version, first seen Oct 17, 2026
- saksham10arora-dotcom/quant-skillsedited, first seen Oct 13, 2026
- sp1e/claude-skillstheir own version, first seen Oct 12, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- saksham10arora-dotcom/quant-skills★ 0100% same
Wrote their own version · 7
- yuiseki/GeoAI-master-skills★ 3same name
- GentleZeal/DirtyData-Killer★ 1same name
- jpoindexter/theft-kit★ 1same name
- motao123/dev-workflow-kit★ 1same name
- Nomanriaz786/claude-consulting-team★ 1same name
- sp1e/claude-skills★ 1same name
- Suryanandx/qvac-ui★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- llms.txtllms.txt
- alpha-zooSkill
- breadth-chart-analystSkill
- canslim-screenerSkill
- factor-mining-pandaaiSkill
- backtesting-bias-avoidanceSkill
- backtest-reviewSkill
- paper-reproSkill
- pine-backtesterSkill
- stats-test-pickerSkill
- vectorbt-backtestSkill
- vectorbt-optimizeSkill
- akquantSkill
- ashare-pre-st-filterSkill
- cninfo-disclosureSkill
- ctp-apiSkill
- ptrade-strategy-writingSkill
- quant-buddySkill
- ssquant-futuresSkill
- tdxquantSkill
- tqsdk-tradingSkill
- wencai-screenerSkill
- defillama-dataSkill
- defillama-flowsSkill
- defillama-yieldsSkill
- perp-funding-basisSkill
- pine-debuggerSkill
- pine-developerSkill
- edgar-financialsSkill
- llmquant-equitiesSkill
- llmquant-macroSkill
- llmquant-riskSkill
- openquant-tradingSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Run this audit BEFORE any modeling conversation gets serious.
- Distinctive: line 40
Never silently drop or impute without reporting which rows/columns were affected.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!--
Imported from: https://github.com/saksham10arora-dotcom/quant-skills
Source Path: skills/data-quality-audit/SKILL.md
Curated for awesome-quant-skills
-->name: data-quality-audit description: Systematically audit a dataset before modeling: nulls, leakage, duplicates, dtype lies, target contamination. Use when the user loads a new dataset, mentions cleaning data, or before any ML/analysis task on unfamiliar data.
Data Quality Audit
Run this audit BEFORE any modeling conversation gets serious. Work through the phases; report findings as a table at the end.
Phase 1: Shape and identity
- Rows x columns; do they match the user's expectation?
- Primary key exists? Duplicated keys?
- Date ranges: gaps, duplicates, future dates
- Grain check: is each row really one entity-time unit? Aggregate and count to verify
Phase 2: Dtype lies
Print dtypes and challenge them:
- Numeric columns loaded as object (commas, currency symbols, whitespace)
- IDs and zip codes as integers (leading zeros destroyed)
- Dates as strings with mixed formats in one column
- Booleans as 0/1/2
Fix dtype issues before computing anything else; null-rate statistics lie otherwise.
Phase 3: Missingness forensics
For every column with any nulls:
- Null rate
- Is missingness correlated with the target? (compute it; if yes, the missingness IS signal)
- Structured missing vs random: sort by another column and look for runs
Never silently drop or impute without reporting which rows/columns were affected.
Phase 4: Leakage scan
The highest-value phase:
- Any column that could not be known at prediction time? Flag it
- Aggregates computed over periods overlapping the label window?
- Target-derived features disguised (ratios containing the outcome)?
- Post-outcome statuses (charge-offs, cancellations) present as features?
Phase 5: Distribution shocks
- Train/test drift on numeric features (report top 5 by KS-statistic)
- Categorical cardinality explosions between splits
- Constant or near-constant columns
- Extreme outliers: count beyond 5 sigma per column; ask if they are errors before winsorizing
Report format
AUDIT: <dataset name>
Rows: N | Cols: M | Memory: X
BLOCKERS: [issues that invalidate modeling until fixed]
WARNINGS: [issues that bias results]
OK: [what was checked and passed]Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

