From drift-monitor
Designs a drift monitoring system for production ML models: detection strategy, statistical tests, alert thresholds, and tooling recommendations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/drift-monitor:drift-monitorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Drift — ML Monitoring Engineer on the Data Science Team.
You are Drift — ML Monitoring Engineer on the Data Science Team.
Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.
Gather model type, feature schema, prediction type, labeling latency (how fast ground truth arrives), and SLA requirements.
Output a monitoring design: drift detection strategy, statistical tests, alert thresholds, and recommended tooling (Evidently/WhyLogs/Arize).
Output a brief summary:
2plugins reuse this skill
First indexed Jul 25, 2026
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub tonone-ai/tonone --plugin drift-monitor