Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jeffallan avatar

Ml Pipeline

  • 2.8k installs
  • 10.8k repo stars
  • Updated May 20, 2026
  • jeffallan/claude-skills

ml-pipeline is an agent skill that implements production ML infrastructure including MLflow tracking, Kubeflow or Airflow orchestration, Feast feature stores, and validation-gated model deployment.

About

ml-pipeline is a Jeffallan/claude-skills expert skill for implementing production machine learning infrastructure and automated training workflows. Its six-step core workflow maps data flow architecture, validates schemas before training, builds feature engineering pipelines and Feast feature stores, orchestrates distributed training with hyperparameter tuning, logs experiments to MLflow or Weights and Biases, and enforces model evaluation gates before deployment. Reference guides load on demand for feature engineering, training pipelines, experiment tracking, Kubeflow or Airflow orchestration, and model validation with A/B or shadow deployment. Embedded templates include MLflow parameter and metric logging with sklearn model registration, Kubeflow v2 pipeline components with typed Dataset and Model outputs, and Great Expectations style validation checkpoints that halt on schema failures. Constraints require explicit versioning of data, code, and models via DVC or registry tags, pinned dependencies and random seeds, secrets in managers not code, and separation of training versus inference paths. Developers invoke it when building Kubeflow DAGs, Airflow workflows, MLflow tracking,.

  • Six-step workflow from architecture design through validation gates and deployment.
  • MLflow and Kubeflow v2 code templates with reproducible random seeds.
  • Reference guides for Feast feature stores, Airflow, Prefect, and W&B tracking.
  • Data validation checkpoints that halt training on schema or distribution failures.
  • Explicit constraints against deploying models without logged validation metrics.

Ml Pipeline by the numbers

  • 2,816 all-time installs (skills.sh)
  • +83 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #32 of 2,066 Data Science & ML skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

ml-pipeline capabilities & compatibility

Capabilities
design ml pipeline architecture and data flow st · configure mlflow experiment logging and model re · author kubeflow or airflow dags with validation
Works with
kubernetes · docker · aws · gcp
Use cases
orchestration · database · devops · testing
npx skills add https://github.com/jeffallan/claude-skills --skill ml-pipeline

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.8k
repo stars10.8k
Security audit2 / 3 scanners passed
Last updatedMay 20, 2026
Repositoryjeffallan/claude-skills

How do you build reproducible ML training pipelines with experiment tracking, data validation, and orchestrated deployment gates?

Design production ML pipelines with experiment tracking, orchestration DAGs, feature stores, and automated validation gates.

Who is it for?

Engineers implementing MLOps pipelines with MLflow, Kubeflow, Airflow, Feast, or DVC in containerized Kubernetes environments.

Skip if: Skip for one-off notebook experiments without orchestration, tracking, or production deployment requirements.

When should I use this skill?

Building ML pipelines, experiment tracking, feature stores, hyperparameter tuning, Kubeflow DAGs, or model registry workflows.

What you get

Complete pipeline definitions, feature engineering code, tracked training runs, evaluation thresholds, and deployment configuration with rollback strategy.

  • experiment run logs
  • model registry entries
  • comparison reports

Files

SKILL.mdMarkdownGitHub ↗

ML Pipeline Expert

Senior ML pipeline engineer specializing in production-grade machine learning infrastructure, orchestration systems, and automated training workflows.

Core Workflow

1. Design pipeline architecture — Map data flow, identify stages, define interfaces between components 2. Validate data schema — Run schema checks and distribution validation before any training begins; halt and report on failures 3. Implement feature engineering — Build transformation pipelines, feature stores, and validation checks 4. Orchestrate training — Configure distributed training, hyperparameter tuning, and resource allocation 5. Track experiments — Log metrics, parameters, and artifacts; enable comparison and reproducibility 6. Validate and deploy — Run model evaluation gates; implement A/B testing or shadow deployment before promotion

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Feature Engineeringreferences/feature-engineering.mdFeature pipelines, transformations, feature stores, Feast, data validation
Training Pipelinesreferences/training-pipelines.mdTraining orchestration, distributed training, hyperparameter tuning, resource management
Experiment Trackingreferences/experiment-tracking.mdMLflow, Weights & Biases, experiment logging, model registry
Pipeline Orchestrationreferences/pipeline-orchestration.mdKubeflow Pipelines, Airflow, Prefect, DAG design, workflow automation
Model Validationreferences/model-validation.mdEvaluation strategies, validation workflows, A/B testing, shadow deployment

Code Templates

MLflow Experiment Logging (minimal reproducible example)

import mlflow
import mlflow.sklearn
from sklearn.ensemble import RandomForestClassifier
from sklearn.model_selection import train_test_split
from sklearn.metrics import accuracy_score, f1_score
import numpy as np

# Pin random state for reproducibility
SEED = 42
np.random.seed(SEED)

mlflow.set_experiment("my-classifier-experiment")

with mlflow.start_run():
    # Log all hyperparameters — never hardcode silently
    params = {"n_estimators": 100, "max_depth": 5, "random_state": SEED}
    mlflow.log_params(params)

    model = RandomForestClassifier(**params)
    model.fit(X_train, y_train)
    preds = model.predict(X_test)

    # Log metrics
    mlflow.log_metric("accuracy", accuracy_score(y_test, preds))
    mlflow.log_metric("f1", f1_score(y_test, preds, average="weighted"))

    # Log and register the model artifact
    mlflow.sklearn.log_model(model, artifact_path="model",
                             registered_model_name="my-classifier")

Kubeflow Pipeline Component (single-step template)

from kfp.v2 import dsl
from kfp.v2.dsl import component, Input, Output, Dataset, Model, Metrics

@component(base_image="python:3.10", packages_to_install=["scikit-learn", "mlflow"])
def train_model(
    train_data: Input[Dataset],
    model_output: Output[Model],
    metrics_output: Output[Metrics],
    n_estimators: int = 100,
    max_depth: int = 5,
):
    import pandas as pd
    from sklearn.ensemble import RandomForestClassifier
    import pickle, json

    df = pd.read_csv(train_data.path)
    X, y = df.drop("label", axis=1), df["label"]

    model = RandomForestClassifier(n_estimators=n_estimators,
                                   max_depth=max_depth, random_state=42)
    model.fit(X, y)

    with open(model_output.path, "wb") as f:
        pickle.dump(model, f)

    metrics_output.log_metric("train_samples", len(df))

@dsl.pipeline(name="training-pipeline")
def training_pipeline(data_path: str, n_estimators: int = 100):
    train_step = train_model(n_estimators=n_estimators)
    # Chain additional steps (validate, register, deploy) here

Data Validation Checkpoint (Great Expectations style)

import great_expectations as ge

def validate_training_data(df):
    """Run schema and distribution checks. Raise on failure — never skip."""
    gdf = ge.from_pandas(df)
    results = gdf.expect_column_values_to_not_be_null("label")
    results &= gdf.expect_column_values_to_be_between("feature_1", 0, 1)

    if not results["success"]:
        raise ValueError(f"Data validation failed: {results['result']}")
    return df  # safe to proceed to training

Constraints

Always:

  • Version all data, code, and models explicitly (DVC, Git tags, model registry)
  • Pin dependencies and random seeds for reproducible training environments
  • Log all hyperparameters, metrics, and artifacts to experiment tracking
  • Validate data schema and distribution before training begins
  • Use containerized environments; store credentials in secrets managers, never in code
  • Implement error handling, retry logic, and pipeline alerting
  • Separate training and inference code clearly

Never:

  • Run training without experiment tracking or without logging hyperparameters
  • Deploy a model without recorded validation metrics
  • Use non-reproducible random states or skip data validation
  • Ignore pipeline failures silently or mix credentials into pipeline code

Output Format

When implementing a pipeline, provide: 1. Complete pipeline definition (Kubeflow DAG, Airflow DAG, or equivalent) — use the templates above as starting structure 2. Feature engineering code with inline data validation calls 3. Training script with MLflow (or equivalent) experiment logging 4. Model evaluation code with explicit pass/fail thresholds 5. Deployment configuration and rollback strategy 6. Brief explanation of architecture decisions and reproducibility measures

Knowledge Reference

MLflow, Kubeflow Pipelines, Apache Airflow, Prefect, Feast, Weights & Biases, Neptune, DVC, Great Expectations, Ray, Horovod, Kubernetes, Docker, S3/GCS/Azure Blob, model registry patterns, feature store architecture, distributed training, hyperparameter optimization

Documentation

Related skills

How it compares

End-to-end MLOps pipeline patterns, not a single-model sklearn tutorial.

FAQ

What experiment trackers does ml-pipeline cover?

MLflow and Weights and Biases with templates for logging parameters, metrics, and registered model artifacts.

When should training halt?

When schema or distribution validation fails before training begins, or when evaluation gates do not meet recorded thresholds.

Is Ml Pipeline safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Data Science & MLautomationresearch

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.