mle-workflow

Guides production machine learning workflows covering data contracts, training, evaluation, deployment, and monitoring.

Updated May 7, 2026
One-click install
npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill mle-workflow-mirzadham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mle-workflow
Source: https://github.com/mirzadham/trainingroombookingsystem2/tree/main/.agent/.agents/skills/mle-workflow
Command: npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill mle-workflow-mirzadham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning notebook experiments into production ML systems often fails due to data leakage, irreproducible training, missing promotion gates, and absent monitoring. This Skill provides a structured workflow that converts model work into reviewable, deployable, and operable systems. ## Core Features & Use Cases - Data and Prediction Contracts: Define entity grain, label timing, feature freshness, split policy, and leakage checks before writing model code. - Reproducible Training and Promotion Gates: Pin configs, seeds, and dataset versions, then enforce automated metric gates comparing against baselines and production models. - Deployment and Operations: Package versioned artifacts with preprocessing, validate serving contracts, and monitor drift, latency, and delayed labels with rollback plans. - Use Case: When converting a churn-prediction notebook into a production service, use this Skill to produce a data contract, baseline scorer, promotion gate tests, a versioned artifact, and a canary rollout plan with rollback triggers. ## Quick Start Use the mle-workflow skill to plan a production pipeline for my classification model, including the data contract, evaluation gates, and rollback strategy.

Frequently Asked Questions about mle-workflow

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

FAQPage Schema
How do I turn a machine learning notebook into a production pipeline?▼

Start by defining a prediction contract and data contract, then move training code into typed configs with pinned dependencies, seeds, and dataset versions. Add promotion gates comparing against a baseline, package preprocessing with the artifact, and plan monitoring plus rollback before launch.

How do I prevent data leakage in ML training pipelines?▼

Check every feature against prediction-time availability and use point-in-time joins with explicit feature and label timestamps. Remove any feature joined using future information, and define train, validation, and test split policies that respect event time.

What metrics should gate ML model promotion to production?▼

Choose metrics from failure costs: precision when false positives dominate, recall when misses dominate, plus calibration, slice metrics, latency, and cost guardrails. Always compare against a baseline and the current production model, and declare do-not-ship thresholds before training finishes.

How do I monitor a machine learning model after deployment?▼

Track system signals like latency and error rates alongside feature drift, prediction distribution drift, and delayed label health. Maintain per-version dashboards for canaries and define rollback triggers naming the previous artifact and traffic-switch mechanism.

When should I avoid adding heavyweight MLOps tooling?▼

Skip heavy machinery when a data contract, baseline, eval script, and rollback note would make the change reviewable. Not every model needs a feature store, GPUs, A/B tests, or real-time feedback; scale the workflow to the actual system.