Skip to content
Back to skills

Data Preparation

ASecurity

Data Preparation. Clean, join and split data without leakage - data cleaning, joins and merges with row-count checks, deduplication, missing value imputation, type fixes, outlier handling, train test split, validation split, cross-validation folds, stratified, group-aware and time-series (forward-chaining) splits, scikit-learn Pipeline and ColumnTransformer. Use for data wrangling, preprocessing, data cleaning, ETL for machine learning, or any request to prepare data for a model. CRISP-DM Dat...

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
datapythongo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add Harrypatria/data-mining-ml --skill data-preparation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Data Preparation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Data Preparation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/harrypatria-data-preparation/badge)](https://www.skillsdirectory.com/skills/harrypatria-data-preparation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: data-preparation
description: Data Preparation. Clean, join and split data without leakage - data cleaning, joins and merges with row-count checks, deduplication, missing value imputation, type fixes, outlier handling, train test split, validation split, cross-validation folds, stratified, group-aware and time-series (forward-chaining) splits, scikit-learn Pipeline and ColumnTransformer. Use for data wrangling, preprocessing, data cleaning, ETL for machine learning, or any request to prepare data for a model. CRISP-DM Data Preparation.
---

# Data Preparation

Every transformation is either a deterministic cleaning step (applied once, before splitting, with no learned statistics) or a learned step (fitted inside the pipeline on training folds only). Mixing them up is the most common leak.

## Order of work

1. **Deterministic cleaning, before the split.** Fix types, parse dates, standardize units and category spellings, remove exact duplicates, drop rows with an invalid target, remove post-event columns. Print the row count after each step.
2. **Joins with assertions.**
   ```python
   n = len(left)
   out = left.merge(right, on="customer_id", how="left", validate="many_to_one")
   assert len(out) == n, f"join changed rows: {n} -> {len(out)}"
   ```
3. **Choose the split** from the data (`references/split-strategies.md`):
   - Independent rows, classification: stratified.
   - Repeated entities: group-aware (`GroupKFold`, `StratifiedGroupKFold`, `GroupShuffleSplit`).
   - Time-ordered data: forward-chaining (`TimeSeriesSplit` or a cutoff date), with a gap equal to the label horizon.
   Fix and record the seed. Hold out the test set now; it is touched once, at evaluation.
4. **Learned steps inside the pipeline.** Imputers, scalers, encoders, winsorizers, selectors, resamplers and target encoders go into a `ColumnTransformer` and `Pipeline` (or an imbalanced-learn `Pipeline` when resampling). Fit happens on training folds only, through cross-validation or one `fit` on the training split.
5. **Document** every transformation in the feature dictionary: what, why, and when the input is available.

## Missing values

| Mechanism | Default |
|---|---|
| MCAR, small share | `SimpleImputer(strategy="median")` |
| MAR | `IterativeImputer` or `KNNImputer` inside the pipeline |
| MNAR or informative | Imputer with `add_indicator=True`; state the assumption |
| Inference (statistics, not prediction) | Multiple imputation, pooled estimates |

Never fill with a statistic computed on the full frame before splitting.

## Outliers

Decide error or signal first. Errors are fixed or removed with a written rule and a count. Signal is kept and handled with robust scaling, winsorizing inside the pipeline, or robust losses.

## Checks before modeling

- `X_train.shape`, `X_test.shape`, positive counts per split, no shared entity ids across splits.
- `df.duplicated().sum()` before splitting is zero or explained.
- No column recorded after the prediction time.
- The pipeline object prints cleanly and `pipeline.fit(X_train, y_train)` runs.

Conditions that change preparation (skew, zero inflation, high cardinality, drift): `data-profiling/references/scenarios.md`.

Files in this skill

  • SKILL.md3.1 KB
  • references/split-strategies.md2.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.