ml-science-discipline

Enforce rigorous ML experimental design with leakage controls and publication-standard reporting.

46|4|Updated Apr 8, 2023
One-click install
npx skills add https://github.com/CRAG666/dotfiles --skill ml-science-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ml-science-discipline
Source: https://github.com/CRAG666/dotfiles/tree/main/skills/ml-science-discipline
Command: npx skills add https://github.com/CRAG666/dotfiles --skill ml-science-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you prevent invalid machine learning results by enforcing rigorous experimental design, leakage controls, and publication-standard reporting practices.

Core Features & Use Cases

  • Reproducible, hypothesis-first experimentation: define falsifiable hypotheses, pre-register the primary metric and baselines, and report multi-seed variance instead of single lucky runs.
  • Leakage-proof data splitting and evaluation: enforce sealed test-set usage, choose the correct split strategy (stratified, group, temporal), and audit preprocessing to ensure fit happens only on training data.
  • Q1-ready evaluation and reporting artifacts: select appropriate metrics, run statistical comparisons with effect sizes, include calibration/uncertainty, and plan external validation against distribution shift.

Quick Start

Use ml-science-discipline when you are about to design or review an ML experiment intended for a paper, such as dataset splitting, evaluation planning, and reporting results you want to defend in peer review.

Frequently Asked Questions about ml-science-discipline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent data leakage when preprocessing machine learning pipelines?

Prevent data leakage by enforcing leakage-resistant preprocessing that fits transformations only on training data. This ensures preprocessing happens before splitting or strictly within cross-validation folds, keeping the test set sealed and preventing invalid model evaluation.

What is the best way to design cross-validation for tuning machine learning models?

The best way to design cross-validation for tuning is using nested cross-validation. This separates hyperparameter tuning from model evaluation, ensuring the test set remains sealed and providing multi-seed reporting variance for publication-grade statistical testing.

How do I report machine learning results for peer review?

Report machine learning results for peer review by generating compliance-oriented artifacts aligned with AI reporting standards. Include statistical comparisons with effect sizes, calibration and uncertainty metrics, and multi-seed variance rather than single lucky runs.

When do I need stratified versus group data splitting in ML experiments?

You need stratified splitting to maintain class proportions, group splitting to prevent patient or cluster leakage, and temporal splitting for time-series data. Choosing the correct split strategy ensures valid decision-relevant claims and a sealed test set.

How do I plan external validation for distribution shift in ML models?

Plan external validation for distribution shift by designing experiments that test models against out-of-distribution data. This involves selecting appropriate metrics and running statistical testing to verify model performance and calibration under realistic deployment conditions.

Why should I pre-register hypotheses and baselines for ML experiments?

Pre-register hypotheses and baselines to enforce reproducible, hypothesis-first experimentation. Defining falsifiable hypotheses and your primary metric before training prevents p-hacking and ensures publication-standard, decision-relevant claims.