Agent skill · Data & Analytics

scientific-data-preprocessing

⚠️ CRITICAL USER EXPERIENCE-BASED SKILL - ALWAYS CONSULT BEFORE DATA PREPROCESSING ⚠️ Prevents catastrophic errors (88.9% error rate in V1.0 case study) through multi-level feature analysis, data leakage detection, and semantic validation. MANDATORY for: data preprocessing, feature engineering, standardization, normalization, interpolation, missing value handling, feature selection, or ANY data transformation task. Covers grouped time-series, cross-sectional, panel data. Detects: time travel leakage, causal inversion, ID misuse, semantic-numeric fallacies, distribution blindness. User's hard-w

foryourhealth111-pixelgithub.com/foryourhealth111-pixelGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add foryourhealth111-pixel/Vibe-Skills --skill scientific-data-preprocessing --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 8
SKILL.md size: 19 KB
Bundled scripts: none
Path: bundled/skills/scientific-data-preprocessing/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,593
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

This skill instructs the agent to consult before any data preprocessing task to prevent catastrophic errors, using multi-level feature analysis, data leakage detection, and semantic validation across grouped data (time-series, panel). It mandates consultation for planning, reflection, and auditing, and provides concrete patterns for data type classification, within-group vs global processing decisions, and various preprocessing steps such as imputation, scaling, encoding, feature engineering, and sliding window features. It emphasizes that the task remains limited to preprocessing and does not decide modeling choices.

How it works

  • Triggered before, during, and after preprocessing to ensure audit and validation at each stage.
  • Guides the agent through a structured workflow: classify features (binary, categorical, continuous), assess data structure (grouped time-series, panel data), validate data quality, handle missing values within groups, encode categoricals, standardize features within groups or globally depending on scope, and create window-based features for momentum.
  • Includes concrete code patterns and examples for within-group interpolation, within-group standardization, one-hot encoding, and sliding window features, as well as checks for data leakage (ID leakage, causal inversion, meaningless numeric codes) and data quality validation.
  • Provides a decision tree to choose processing scope (within_group vs global) using intraclass correlation-based logic and a pattern for automatic scope detection.
  • Supplies guardrails and boundaries: does not handle purely cross-sectional data, does not choose models, and assumes data fits in memory.

When to use it

  • Trigger keywords include: preprocess, preprocessing, data cleaning, data preparation, standardize, normalize, scale, transform, impute, fill missing, handle NaN, encode, one-hot, categorical, feature engineering, feature selection, feature construction, train test split, cross validation split, interpolate, smooth, aggregate.
  • Use at the mandatory checkpoints: BEFORE planning preprocessing strategy, DURING reflection and error checking, AFTER comprehensive validation and audit.
  • Applicable to data with groups (e.g., match_id, patient_id, session_id) and when goal is within-group or cross-group comparison guided by stability of variance.

What it can touch

  • The skill references tools/libraries in examples such as pandas (pd), scikit-learn (StandardScaler, OneHot), numpy, scipy for interpolation and scaling, and groupby transforms. It also shows usage of functions like get_dummies, interpolate, rolling, and StandardScaler.
  • It specifies inputs required before proceeding: confirmation of groups, understanding of within-group vs cross-group goal, and domain constraints on data ranges/units.

Caveats

  • License: Apache-2.0 (as per the repository metadata).
  • It does not make domain-specific feature engineering decisions; business logic must be supplied by the user.
  • It does not handle distributed/big data infrastructure; assumes data in memory.
  • It warns about potential pitfalls like cross-group interpolation, time-travel leakage, and misinterpreting IDs as numeric features.
From the SKILL.md

# Scientific Data Preprocessing Skill ⚠️ **CRITICAL: USER'S HARD-WON EXPERIENCE - MANDATORY CONSULTATION** ⚠️ This skill encapsulates painful lessons learned from real preprocessing disasters (88.9% error rate documented). **ALWAYS use this skill for planning, reflection, and validation when ANY data preprocessing is involved.** **Why this skill is mandatory:** - Based on actual project failures (

More from Vibe-Skills
All skills →
About this skill
What does the scientific-data-preprocessing skill do?

⚠️ CRITICAL USER EXPERIENCE-BASED SKILL - ALWAYS CONSULT BEFORE DATA PREPROCESSING ⚠️ Prevents catastrophic errors (88.9% error rate in V1.0 case study) through multi-level feature analysis, data leakage detection, and semantic validation. MANDATORY for: data preprocessing, feature engineering, standardization, normalization, interpolation, missing value handling, feature selection, or ANY data transformation task. Covers grouped time-series, cross-sectional, panel data. Detects: time travel leakage, causal inversion, ID misuse, semantic-numeric fallacies, distribution blindness. User's hard-w

How do I install it?

Run `npx skills add foryourhealth111-pixel/Vibe-Skills --skill scientific-data-preprocessing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From foryourhealth111-pixel/Vibe-Skills, a repository with 2,593 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going