exploratory-data-analysis
/exploratory-data-analysis
Use when starting on a new dataset, before modeling, or when asked to "explore", "profile", "understand", or "summarize" data. Covers structured EDA, distributions, correlations, target leakage checks, and visualization.
- Author
- param087 ↗
- Repository
- agent-ml-skills ↗
- Licence
- MIT
- Last repository change
- 05.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when starting on a new dataset, before modeling, or when asked to "explore", "profile", "understand", or "summarize" data. Covers structured EDA, distributions, correlations, target leakage checks, and visualization.
Triggers from the description
Original author description
Use when starting on a new dataset, before modeling, or when asked to "explore", "profile", "understand", or "summarize" data. Covers structured EDA, distributions, correlations, target leakage checks, and visualization.
How it works
- Overview
- When to use
- Workflow
- Reference snippet
- Pitfalls
- Hand-off
SKILL.md preview
---
name: exploratory-data-analysis
description: Use when starting on a new dataset, before modeling, or when asked to "explore", "profile", "understand", or "summarize" data. Covers structured EDA, distributions, correlations, target leakage checks, and visualization.
---
# Exploratory Data Analysis (EDA)
## Overview
EDA is the disciplined first pass over a dataset: understand shape, types, distributions, missingness, relationships, and red flags **before** writing a single model. Skipping it is the #1 cause of silent modeling failures (leakage, broken splits, garbage features).
## When to use
- A new dataset just landed.
- You're asked to "look at", "profile", "explore", or "summarize" data.
- A model underperforms and you need to understand the inputs.
## Workflow
Follow this order. Do not jump to modeling until every step is answered.
1. **Shape & types** — rows, columns, dtypes, memory. Are numeric columns actually numeric?
2. **Missingness** — per-column null counts and patterns (MCAR/MAR/MNAR). Is missingness itself predictive?
3. **Target analysis** — distribution of the target (class balance / skew). This decides metrics and resampling.
4. **Univariate** — distributions of each feature (histograms, value counts, describe()).
5. **Bivariate** — feature vs target relationships; correlation matrix for numeric.
6. **Leakage scan** — features too perfectly correlated with the target, IDs, timestamps, or post-outcome columns.
7. **Cardinality & outliers** — high-cardinality categoricals, extreme values.
## Reference snippet
```python
import pandas as pd
df = pd.read_csv("data.csv")
# 1. Shape & types
print(df.shape)
print(df.dtypes.value_counts())
print(df.memory_usage(deep=True).sum() / 1e6, "MB")
# 2. Missingness
miss = df.isna().mean().sort_values(ascending=False)
print(miss[miss > 0])
# 3. Target (classification example)
print(df["target"].value_counts(normalize=True))
# 4-5. Numeric summary + correlations with target
num = df.select_dtypes("number")
print(num.describe().T)
print(num.corr()["target"].sort_values(ascending=False))
# 6. Leakage red flag: |corr| ~ 1.0 with target
corr_t = num.corr()["target"].drop("target").abs()
print("LEAKAGE SUSPECTS:", corr_t[corr_t > 0.95].index.tolist())
```
For a fast automated first look, `ydata-profiling` (`ProfileReport(df)`) or `df.describe(include="all")` is acceptable — but never let a tool replace the manual leakage scan.
## Pitfalls
- **Profiling on the full dataset then splitting.** EDA that informs feature choices must be done on the **training split only**, or you leak test information.
- **Ignoring class imbalance.** A 99/1 split makes accuracy meaningless — note it now so you pick the right metric later.
- **Treating IDs as features.** Order IDs, row indices, and hashes correlate with the target by accident.
- **Trusting `.corr()` for non-linear / categorical relationships.** Use mutual information or grouped means for those.
## Hand-off
Output of EDA should be: a short written summary (shape, target balance, top missing columns, leakage suspects, candidate features) that downstream steps (data-cleaning, feature-engineering) consume.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · param087/agent-ml-skills | 100 | MIT |
| jaechang-hits/SciAgent-Skills | 100 | MIT |
| lamm-mit/scienceclaw | 100 | Apache-2.0 |
| fmschulz/omics-skills | 100 | MIT |
| aipoch/medical-research-skills | 100 | MIT |
| seb1n/awesome-ai-agent-skills | 98 | MIT |
| davila7/claude-code-templates | 95 | MIT |
| JPeetz/agent-skills | 93 | MIT |
| Amey-Thakur/AI-SKILLS | 90 | MIT |
Database snapshot: 13.11.2026 · package version 8487912df518 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 98eda-report
Run exploratory data analysis on a dataset and produce a structured report. Use when the user says "explore this dataset", "EDA on X", "analyze this data", "what's in this dataset", "summarize this data", "first look at the data", "understand this dataset before modeling", "data… - 90programmatic-eda
Systematic exploratory data analysis. Activate when a dataset needs profiling — structure check, nulls, outliers, distributions, correlations — before deeper analysis begins. - 90plot-eda
Design an exploratory data analysis workflow for a dataset. Use when asked to "explore this dataset", "run an EDA", or "what is in this data". - 100data-profiling
Data Profiling. Explore and profile a dataset before modeling - EDA (exploratory data analysis), distributions, skew, outliers, missingness (MCAR, MAR, MNAR), duplicates, cardinality, class balance, label quality, leakage risk, bias and representativeness, drift between periods.… - 100eda-playbook
Runs a structured exploratory data analysis on a new or suspect dataset - schema audit, target analysis, feature profiling, missingness patterns, and leakage checks - ending in a written decision log. Use when someone says "I just got this dataset, where do I start", "my model… - 100stat-eda
Conduct Exploratory Data Analysis (EDA) using descriptive statistics, visualizations, and data quality checks. Use this skill when the user has a dataset and needs to understand its structure, find patterns, detect anomalies, or prepare data for further analysis — even if they…