From drift
Audits existing ML monitoring setups to find gaps in drift coverage and missing alerts. Useful for data science teams improving model monitoring.
How this skill is triggered — by the user, by Claude, or both
Slash command
/drift:drift-reconThis 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.
Read existing monitoring code, dashboards, or alerting configs. Grep for drift, PSI, KS, Evidently, WhyLogs.
Report: monitoring coverage gaps, missing drift checks, alert gaps, and recommended improvements.
Output a brief summary:
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
2plugins reuse this skill
First indexed Jul 25, 2026
npx claudepluginhub tonone-ai/tonone --plugin drift