From drift-recon
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-recon: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:
2plugins reuse this skill
First indexed Jul 25, 2026
npx claudepluginhub tonone-ai/tonone --plugin drift-reconGuides 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.