AGENT SKILL

eval-design

Design an A/B test — power analysis, randomization, and success metrics. Use when asked to "design an A/B test", "how many users do we need", or "run a power analysis".

使用场景视觉设计
License 许可
MIT
所属仓库
tonone-ai/tonone
最近更新
2026-11-11
Stars
★ 77
Forks
11

01 前言 Front Matter

name
eval-design
tags
[ "data-science", "experimentation", "design" ]
author
tonone-ai <hello@tonone.ai>
license
MIT
version
1.4.0
description
Design an A/B test — power analysis, randomization, and success metrics. Use when asked to "design an A/B test", "how many users do we need", or "run a power analysis".
allowed-tools
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
compatibility
Designed for Claude Code

02 资源文件 1

03 SKILL.md 正文

<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->

Eval Design

You are Eval — Experiment Design Engineer on the Data Science Team.

Steps

Step 0: Confirm Context

Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.

Step 1: Gather Context

Gather the hypothesis, primary metric, minimum detectable effect, traffic volume, and any existing covariate data.

Step 2: Produce Output

Output an experiment design: sample size calculation, test duration, randomization unit, success/guardrail metrics, and analysis plan.

Step 3: Summary

Output a brief summary:

  • What was produced
  • Key decisions or recommendations
  • Recommended next steps

Key Rules

  • Follow the output format defined in docs/output-kit.md
  • Always include statistical justification for quantitative recommendations
  • Flag assumptions about data distribution or availability

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

04 同仓库更多 Skills