mlops-engineer

Designs and hardens model lifecycle infrastructure from training through production serving.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/sumitake/agent-collab --skill mlops-engineer-sumitake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mlops-engineer
Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/mlops-engineer
Command: npx skills add https://github.com/sumitake/agent-collab --skill mlops-engineer-sumitake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Models that work in training often fail silently in production because of unversioned artifacts, missing promotion gates, untested rollback paths, and monitoring that tracks infrastructure health but not prediction quality. This Skill diagnoses the weakest link in a model lifecycle and scopes the smallest fix that closes the gap. ## Core Features & Use Cases - Lifecycle Gap Analysis: Traces the end-to-end path from training run to production endpoint and identifies nondeterministic builds, unversioned artifacts, or unenforced promotion gates. - Registry and Rollout Design: Designs model registries with lineage from raw data to deployed weights, plus canary, shadow-traffic, and rollback strategies with bounded blast radius. - Drift and Quality Monitoring: Distinguishes infrastructure health (latency, error rate) from model health (prediction distribution shift, feature drift) and wires alerts to each. - Use Case: A team deploys models by copying files to a serving host with no versioning. Use this Skill to design a versioned registry, an enforced promotion gate, and a pre-tested rollback path before the next release. ## Quick Start Ask the agent to audit your model deployment pipeline and design a promotion gate with a tested rollback path.

Frequently Asked Questions about mlops-engineer

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

FAQPage Schema
How do I set up a model registry for production ML?▼

A model registry needs a versioning scheme, artifact storage, and metadata capture including training data snapshot, hyperparameters, and evaluation results. Every deployed model version should resolve back to the data, code, and hyperparameters that produced it.

How do I deploy a machine learning model to production safely?▼

Use a promotion gate with concrete checkable criteria enforced by the pipeline, then roll out with shadow traffic or canary percentages to bound blast radius. Exercise the rollback path before calling the deployment done.

What is the difference between infrastructure monitoring and model drift monitoring?▼

Infrastructure monitoring tracks latency and error rates, while model monitoring tracks prediction distribution shift, feature drift, and label delay. Infrastructure dashboards can be green while model quality silently degrades, so alerts must be wired to each separately.

Why does a model work in training but fail in production?▼

Training-serving skew comes from unpinned dependencies, container differences, hardware or driver mismatches, and inconsistent feature computation between training and serving. Enumerate environment differences explicitly rather than assuming parity.

When should I not redesign my entire ML platform?▼

Avoid platform-wide redesign when a scoped lifecycle fix resolves the stated problem, such as adding a promotion gate or versioning artifacts. Reserve full overhauls for cases where the user explicitly requests them.