monitoring-data-drift

Detect and rank feature distribution drift in deployed machine learning models.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/rocklambros/rcs --skill monitoring-data-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-data-drift
Source: https://github.com/rocklambros/rcs/tree/main/skills/ml-datasci/monitoring-data-drift
Command: npx skills add https://github.com/rocklambros/rcs --skill monitoring-data-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you determine whether a deployed machine learning model is degrading because the input data has shifted, so you can investigate the cause before retraining.

Core Features & Use Cases

  • Chooses drift metrics by feature type, using PSI for continuous and ordinal features, Jensen-Shannon for categoricals, and proportion checks for booleans.
  • Calibrates alert thresholds against baseline noise, which reduces false alarms on seasonal, high-variance, or cohort-specific features.
  • Produces per-feature drift tables, attribution categories, cohort breakdowns, and root-cause hypotheses for post-deployment monitoring and incident triage.

Quick Start

Ask this skill to compare a stable reference window with current inference traffic, calibrate per-feature drift thresholds, and return the top drifting features with likely root causes.

Frequently Asked Questions about monitoring-data-drift

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

FAQPage Schema
How do I detect feature distribution drift in deployed machine learning models?

Detect feature distribution drift by comparing a stable reference window against current live inference traffic. This process applies per-feature metric selection, baseline-noise calibration, and cohort breakdowns to rank shifting features before any retraining.

What is the best way to reduce false alarms when monitoring model drift on seasonal data?

Reduce false alarms on seasonal data by calibrating alert thresholds against baseline noise. This cooldowned alerting approach prevents triggering false drift warnings on high-variance or cohort-specific features during post-deployment monitoring.

Which drift metrics should I use for different feature types in model monitoring?

Use PSI for continuous and ordinal features, Jensen-Shannon divergence for categoricals, and proportion checks for booleans. This per-feature metric selection ensures accurate distribution drift detection across mixed data types.

How do I find the root cause of model performance degradation before retraining?

Find the root cause of model performance degradation by generating root-cause hypotheses from per-feature drift tables and attribution categories. Investigating cohort breakdowns identifies whether seasonal shifts or live inference traffic changes caused the drop.

Can I use cohort analysis to investigate seasonal or cohort-shift data drift?

Yes, cohort analysis supports seasonal and cohort-shift investigations by producing cohort breakdowns alongside per-feature drift tables. This isolates specific population segments experiencing distribution drift in deployed models.

When should I not retrain my machine learning model after detecting data drift?

Avoid retraining when data drift stems from seasonal baseline noise rather than genuine distribution shifts. Calibrated thresholds and cooldowned alerting ensure you only recommend retraining after validating root-cause hypotheses for the feature shift.