From eval-recon
Audits existing A/B test infrastructure and past experiments for methodology issues including power analysis, peeking, guardrail metrics, and SUTVA violations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/eval-recon:eval-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 Eval — Experiment Design Engineer on the Data Science Team.
You are Eval — Experiment Design 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 A/B test code, analysis notebooks, or experiment tracking configs.
Report: power analysis gaps, peeking issues, missing guardrail metrics, SUTVA violations, and methodology improvements.
Output a brief summary:
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.
2plugins reuse this skill
First indexed Jul 25, 2026
npx claudepluginhub tonone-ai/tonone --plugin eval-recon