model-retraining

Automate ML model retraining pipelines with drift triggers, champion-challenger evaluation, and rollback.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill model-retraining-kalilurrahman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-retraining
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/04-ai-ml/model-retraining
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill model-retraining-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires prefect, mlflow, pandas, numpy, scikit-learn.

What problem does it solve? Machine learning models degrade as real-world data shifts, and manually retraining, validating, and promoting models is error-prone and slow. This Skill designs automated retraining pipelines that safely retrain models, compare challengers against champions, and roll back instantly when production metrics regress. ## Core Features & Use Cases - Retraining Orchestration: Build Prefect flows that fetch recent data, validate quality, engineer features, and train challengers with the champion's hyperparameters. - Champion vs. Challenger Evaluation: Compare models on a held-out test set with minimum improvement thresholds and automated promote/reject decisions via MLflow. - Promotion & Rollback: Automate MLflow stage transitions with approval gates, shadow deployment guidance, and instant rollback to archived versions. - Use Case: A data science team notices prediction drift in their order-propensity model. Use this Skill to design a drift-triggered retraining pipeline that retrains on the last 60 days of data, validates quality, and auto-promotes only if AUC improves. ## Quick Start Design an automated retraining pipeline for my order-propensity model that retrains weekly, compares the challenger against the production champion on a holdout set, and requires manual approval before promotion.

Frequently Asked Questions about model-retraining

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

FAQPage Schema
How do I automate ML model retraining with Prefect?

Build a Prefect flow with tasks for data fetching, quality validation, feature engineering, training, and evaluation, then attach a CronSchedule via Deployment.build_from_flow. The pipeline can run weekly or be triggered by drift detection events.

How to compare challenger vs champion models before promotion?

Evaluate both models on the same held-out test set using metrics like ROC AUC, then promote only if the challenger exceeds a minimum improvement threshold such as 0.005. Log the comparison metrics to MLflow for auditability.

Can MLflow roll back a production model to a previous version?

Yes, MLflow model registry supports stage transitions, so you can archive the current Production version and transition the most recent Archived version back to Production. Keep archived versions for at least 90 days to maintain a real rollback window.

Should retraining require manual approval before promotion?

Scheduled retraining should typically require human approval, while drift-triggered retraining can auto-promote when any improvement is acceptable. High-stakes models should also run in shadow mode alongside the champion before full promotion.

Why does automated retraining produce worse models sometimes?

Common causes include poor data quality, training-serving skew from inconsistent feature transforms, and evaluating on the same test set used for promotion decisions. Validate data quality before training and maintain a truly held-out evaluation set.