mle-workflow

Plans and reviews production ML pipelines with data contracts, promotion gates, and rollback.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill mle-workflow-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mle-workflow
Source: https://github.com/diazMelgarejo/orama-system/tree/main/.cursor/.agents/skills/mle-workflow
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill mle-workflow-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning notebook experiments into production ML systems often fails due to data leakage, irreproducible training, missing evaluation gates, and absent monitoring or rollback paths. This Skill provides a structured workflow that forces explicit data contracts, reproducible pipelines, measurable promotion criteria, and operational monitoring before a model ships. ## Core Features & Use Cases - Prediction and Data 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 the current production model. - Serving, Monitoring, and Rollback: Package versioned artifacts with schema validation, fallback behavior, drift monitoring, and named rollback triggers. - Use Case: When converting a churn-prediction notebook into a production service, use this Skill to produce a data contract, baseline scorer, promotion gate config, canary rollout plan, and observation ledger as reviewable artifacts. ## Quick Start Ask the agent to use the mle-workflow skill to plan a production pipeline for your model, starting with the prediction contract and data contract.

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 notebook model into a production ML pipeline?

Start by defining a prediction contract and data contract covering entity grain, label timing, and feature freshness. Then make training reproducible with pinned configs, seeds, and dataset versions, and add automated promotion gates before packaging a versioned serving artifact.

How do I prevent data leakage in machine learning features?

Check every feature against prediction-time availability and use point-in-time joins with explicit feature and label timestamps. Remove or isolate any feature joined using future information, and use time-based splits instead of random splits.

What metrics should gate ML model promotion to production?

Declare gates before training: a primary metric aligned to product behavior, plus guardrails for calibration, latency, cost, and slice performance. Always compare against a baseline and the current production model, and fail closed when required metrics are missing.

Does this workflow apply to LLM and embedding pipelines?

Yes, the workflow covers LLM workflows, embeddings, ranking, forecasting, and anomaly detection, not just supervised classifiers. It calibrates scope so you only add machinery like feature stores or A/B tests when the system actually needs them.

How do I monitor an ML model after deployment?

Track system signals like latency and error rate alongside feature drift, prediction distribution drift, and delayed-label health. Every deployment should name a rollback artifact, config, and traffic-switch trigger before launch.

When should I not add heavy MLOps infrastructure?

Skip heavyweight machinery when a data contract, baseline, eval script, and rollback note are enough to make the change reviewable. The workflow explicitly warns against forcing one architecture onto every model or assuming labels, GPUs, or real-time feedback exist.