model-monitoring

Designs layered monitoring for production ML models covering drift, delayed labels, and segment quality.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill model-monitoring-snoodleboot-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: model-monitoring
Source: https://github.com/snoodleboot-io/discrecontinual_equations/tree/main/.claude/skills/model-monitoring
Command: npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill model-monitoring-snoodleboot-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production ML models degrade silently: labels arrive weeks late, per-feature drift tests flood alert channels with false positives, and aggregate metrics hide failing segments. This Skill provides the patterns to build a monitoring stack that pages on real problems and distinguishes data bugs from genuine drift. ## Core Features & Use Cases - Layered Alerting Design: Orders monitoring layers by detection latency, from operational metrics to business outcomes, so fast layers page first. - Prediction Drift with PSI: Implements Population Stability Index as an effect-size drift metric that does not degrade at high sample volumes, with threshold-based alert rules. - Delayed Ground Truth Compensation: Covers lagged quality metrics, fast proxy labels, and randomized control holdouts to handle label maturity delays and selection bias. - Use Case: A fraud model's chargeback labels take 60 days to arrive. Use this Skill to set up lagged AUC dashboards, proxy labels from manual review outcomes, and a hash-bucketed control holdout for unbiased error estimates. ## Quick Start Ask the assistant to design a monitoring and alerting plan for a production churn model whose labels arrive 60 days after prediction.

Frequently Asked Questions about model-monitoring

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

FAQPage Schema
How do I detect data drift in production machine learning models?▼

Alert on prediction drift using an effect size like Population Stability Index rather than per-feature tests. Compute PSI by binning the baseline score distribution and comparing against current scores; values above 0.25 indicate a major shift worth paging on.

PSI vs KS test for model drift detection?▼

PSI is preferred at scale because KS test p-values shrink with sample size, making everything significant at millions of predictions per day. PSI is an effect size with stable thresholds: under 0.10 means no shift, 0.10-0.25 warrants investigation, above 0.25 warrants paging.

How do I monitor model quality when labels arrive weeks late?▼

Compute quality metrics only over predictions whose label window has closed, and publish them with the maturity lag stated. Pair these lagged metrics with fast proxy labels, such as manual review outcomes for fraud, and track the proxy-to-true-label correlation.

Why is automatic retraining on drift detection dangerous?▼

Sudden structural drift is often an upstream data bug, such as a renamed column defaulting to null. Retraining on that data bakes the bug into the model weights, so retraining triggers should be gated on data validation passing first.

How do I measure model precision when the model filters the labeled data?▼

Use a small randomized control holdout, such as allowing roughly 0.5% of requests through unscored via hash bucketing. This provides the only unbiased estimate of the true error rate, since the labeled set is otherwise filtered by the model's own decisions.