Skill

Automate ML Pipeline Setup and Optimization

An AutoML pipeline expert that designs modular, production-ready ML pipelines - H2O, MLflow, Airflow orchestration - from ingestion to deployment.

Works with githubh2o.aimlflowvertex aiflaml

78
Spark score
out of 100
Updated 21 days ago
Version 1.0.0
Models

Add to Favorites

Why it matters

Design, implement, and optimize robust, scalable, and production-ready AutoML systems. Automate data preprocessing, feature engineering, model selection, hyperparameter optimization, and deployment.

Outcomes

What it gets done

01

Design modular and scalable AutoML pipeline architectures.

02

Integrate with various AutoML frameworks like H2O.ai, Vertex AI, and AutoGluon.

03

Configure data ingestion, validation, and feature engineering pipelines.

04

Implement experiment tracking with MLflow for comprehensive metadata logging.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-automl-pipeline-setup | bash

Overview

AutoML Pipeline Setup Expert агент

An AutoML pipeline expert that designs modular, reproducible, production-ready ML pipelines: data validation, scikit-learn-based feature engineering, H2O AutoML training, MLflow experiment tracking, and Airflow orchestration end to end. Use it to pick the right AutoML framework for your environment and wire it into a monitored, config-driven pipeline rather than a one-off training script.

What it does

Designs, implements, and optimizes production-ready AutoML pipelines, spanning multiple AutoML frameworks, pipeline-orchestration tools, and MLOps practices. Architecture follows five principles: modular, interchangeable components for ingestion, preprocessing, feature engineering, training, and evaluation; YAML/JSON-driven configuration so parameters can be changed without touching code; horizontal scalability via distributed compute frameworks like Dask, Ray, or Spark; reproducibility through seed management, data/model version control, and deterministic processing; and monitoring built in from the start (logging, metrics collection, alerting). It provides concrete implementations across the pipeline: a data-ingestion and validation class that reads CSV/Parquet and runs Great Expectations checks (minimum row count, column-count bounds); a feature-engineering pipeline built on scikit-learn's ColumnTransformer (median imputation, StandardScaler, variance-threshold filtering for numeric columns; constant-fill imputation and label encoding for categorical columns) plus feature-engine's mathematical feature combination; an H2O AutoML wrapper that trains GBM, RF, XGBoost, DeepLearning, and GLM models and extracts AUC, RMSE, and mean-per-class-error metrics; an MLflow experiment tracker that logs parameters, metrics, the trained model, feature importance, and a run summary; a full YAML pipeline configuration schema (data source, feature-engineering strategy, AutoML framework and algorithm list, deployment mode, compute limits); and an Airflow DAG chaining data validation, feature engineering, AutoML training, and model validation into a daily-scheduled pipeline.

When to use - and when NOT to

Use it to select an AutoML framework for a given environment - H2O.ai for enterprise settings and tabular-data performance, AutoML Tables/Vertex AI for managed Google Cloud deployment, Auto-sklearn/FLAML for research and ensemble customization, MLflow plus Optuna for a custom pipeline with strong experiment tracking, or AutoGluon for rapid prototyping - and to wire that choice into a modular, monitored, reproducible pipeline rather than a one-off training script.

Inputs and outputs

Input is raw training data (CSV or Parquet, or an S3 path per the YAML config) plus a target column, ingested and validated by a class such as AutoMLDataPipeline. Output is a validated, feature-engineered dataset, a trained AutoML model with performance metrics, a logged MLflow experiment run, and an orchestration layer - an Airflow DAG plus a YAML pipeline configuration covering data, feature engineering, AutoML settings, deployment, and compute limits.

Integrations

Built around H2O AutoML, MLflow (experiment tracking, model logging, mlflow.sklearn), Great Expectations for data validation, scikit-learn (ColumnTransformer, Pipeline, StandardScaler, SimpleImputer) and feature-engine for feature engineering, Apache Airflow for DAG orchestration, and distributed-compute frameworks Dask, Ray, and Spark for scaling.

Who it's for

For ML engineers and MLOps teams standing up a production AutoML system rather than a one-off notebook model - it covers performance optimization (stratified sampling for hyperparameter search, time- and performance-based early stopping, memory/CPU resource limits, caching preprocessed data, distributed hyperparameter search via Ray Tune or Dask) and model-selection practices (time-based cross-validation splits for time series, stratified k-fold for classification, weighted-averaging or stacking ensembles of the best-performing models).

data:
  source: "s3://bucket/data.csv"
  target_column: "target"
  validation_split: 0.2
  
feature_engineering:
  numeric_strategy: "median"  # mean, median, mode
  categorical_strategy: "label_encoding"  # one_hot, target_encoding
  feature_selection: true
  variance_threshold: 0.01
  
automl:
  framework: "h2o"  # h2o, autosklearn, autogluon
  max_runtime_seconds: 3600
  max_models: 20
  algorithms: ["GBM", "RF", "XGBoost", "DeepLearning"]
  cross_validation_folds: 5
  
deployment:
  endpoint_type: "batch"  # batch, real_time
  monitoring: true
  model_registry: "mlflow"
  
compute:
  n_jobs: -1
  memory_limit: "8GB"
  distributed: false

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.