a-b-test-design

a-b-test-design is a skill for Claude Code from Owl-Listener/designer-skills. It costs 46 tokens per session (408 once invoked), scanned A, original, MIT.

A plan for comparing two versions of a product change with real usage data. It defines the expected result, the versions to compare, the success measures, and the number of users needed.

In plain words
What is it for?
Use it to prepare controlled experiments for changes that can be measured at scale, such as conversion or task outcomes.
Why use it?
It turns a vague design comparison into a measurable experiment and helps avoid unreliable conclusions from too little data or poorly chosen measures.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the prototyping-testing plugin — 10 skills, 4 commands shipped together

Good fit Use it to prepare controlled experiments for changes that can be measured at scale, such as conversion or task outcomes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/designer-skills/a-b-test-design
About the project

Owl-Listener/designer-skills is a collection of AI-agent skills, commands, and plugins for design work, covering research, design systems, interfaces, interaction, and delivery. Designers and developers use it inside coding assistants to guide design tasks, and the catalogue entries represent selected parts of that larger collection.

Owl-Listener/designer-skills · 3,079 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Owl-Listener/designer-skills --skill a-b-test-design
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designer-skills

Made for: Claude Code.

Or install prototyping-testing, the plugin that ships this one along with the rest of its 10 skills, 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for a-b-test-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designer-skills/a-b-test-design/github.svg)](https://agentmods.dev/skills/owl-listener/designer-skills/a-b-test-design)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designer-skills/a-b-test-design"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/a-b-test-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for a-b-test-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/designer-skills/a-b-test-design"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/a-b-test-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 408 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 14 Sept 2026
  • Snyk pass 14 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.00408
Opus 5.5 $0.00018 $0.00163
Sonnet 5.5 $0.00009 $0.00082
Haiku 4.5 $0.00005 $0.00041

Measured 1mo ago against content hash 2ca225aaae67, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

a-b-test-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

prototyping-testing/skills/a-b-test-design/SKILL.md · 42 lines

What it actually says

A/B Test Design

You are an expert in designing rigorous A/B experiments that produce actionable results.

What You Do

You design A/B tests with clear hypotheses, controlled variants, appropriate metrics, and statistical rigor.

Test Structure

1. Hypothesis

Structured as: 'If we [change], then [outcome] will [improve/decrease] because [rationale].'

2. Variants

  • Control (A): current design
  • Treatment (B): proposed change
  • Keep changes isolated — test one variable at a time

3. Primary Metric

The single most important measure of success. Must be measurable, relevant, and sensitive to the change.

4. Secondary Metrics

Supporting measures and guardrail metrics to detect unintended consequences.

5. Sample Size

Based on: minimum detectable effect, baseline conversion rate, statistical significance level (typically 95%), and power (typically 80%).

6. Duration

Run until sample size is reached. Account for weekly cycles (run in full weeks). Minimum 1-2 weeks typically.

Common Pitfalls

  • Peeking at results before completion
  • Too many variants at once
  • Metric not sensitive enough to detect change
  • Sample size too small
  • Not accounting for novelty effects
  • Ignoring segmentation effects

When Not to A/B Test

  • Very low traffic (insufficient sample)
  • Ethical concerns with withholding improvement
  • Foundational changes that affect everything
  • When qualitative insight is more valuable

Best Practices

  • One hypothesis per test
  • Document everything before starting
  • Don't stop early on positive results
  • Analyze segments after overall results
  • Share learnings broadly regardless of outcome
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 42 lines · 46 tokens per session scan A 2ca225aaae67

Subscribe to this mod's changes

a-b-test-design is a skill published in the GitHub repository Owl-Listener/designer-skills (3,079 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 408 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

ui-review

Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.

LiHongwei-cn/lihongwei-cn · 26 tokens

writing-workflow-skills

Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.

JetBrains/thinkrail · 60 tokens

node-inspect-debugger

See runtime state a console.log cannot reach — set real breakpoints, step, and dump the scope chain of a paused Node/TypeScript process. Use on "set a breakpoint", "inspect runtime state", "console.log isn't enough", "step through this", "what's in this closure at runtime", "attach a debugger". Not a logging or…

BlackBeltTechnology/pi-agent-dashboard · 83 tokens

doc-coauthoring

Collaboratively author technical specifications, RFCs, PRDs, ADRs, and decision documents through structured context gathering, iterative refinement, and blind reader testing. Use when drafting substantial documentation, architecture proposals, or engineering design records.

WrongStack/WrongStack · 50 tokens

micro-animation-gif

Generate compact, optimized animated GIFs for team chat (Slack/Discord), GitHub PRs, release notes, and UI micro-interactions using Pillow or FFmpeg. Use when creating animated emojis, loading spinners, badge animations, or lightweight UI demo loops under tight file-size constraints.

WrongStack/WrongStack · 63 tokens

code-quality

Drive static-analysis code quality in pi-agent-dashboard with Biome (analyze → fix → test), in changed-files or whole-repo mode. Use when asked to "improve code quality", "lint and fix", "clean up warnings", "fix Biome issues", "run static analysis", or when setting a code-quality goal. Skip for one-line edits.

BlackBeltTechnology/pi-agent-dashboard · 77 tokens