ab-testing

Use when designing experiments for subject lines, offers, cadences, or journeys.

16 stars

Best use case

ab-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when designing experiments for subject lines, offers, cadences, or journeys.

Teams using ab-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/ab-testing/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/testing-security/ab-testing/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/ab-testing/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How ab-testing Compares

Feature / Agentab-testingStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when designing experiments for subject lines, offers, cadences, or journeys.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Experimentation & A/B Testing Skill

## When to Use
- Validating new subject lines or creative.
- Testing segmentation hypotheses (persona vs behavior).
- Optimizing cadence, timing, or automation triggers.

## Framework
1. **Hypothesis** – define expected uplift + rationale.
2. **Metric Selection** – primary (open/click/conv) + guardrails (unsubs, spam).
3. **Sample Sizing** – ensure stat significance (min 500 recipients per variant or use power calculator).
4. **Execution** – randomize, keep variants isolated, limit simultaneous tests.
5. **Analysis** – use z-test or Bayesian uplift; document learnings.

## Templates
- Experiment brief (hypothesis, segments, KPI, risk guardrails).
- Variant table (control vs test inputs, creative asset links, owner).
- Calculator sheet for minimum detectable effect + sample size.
- Post-test debrief doc capturing learnings + rollout plan.

## Experiment Ideas
- Subject line vs preview text combos.
- CTA placement (hero vs footer).
- Personalization depth (basic vs dynamic modules).
- Wait times between touches.

## Tips
- Run no more than two tests per journey simultaneously.
- Recycle learnings into playbooks + automation templates.
- Segment results by persona to catch hidden signals.

---

Related Skills

ab-testing-statistician

16
from diegosouzapw/awesome-omni-skill

Expert in statistical analysis for blind A/B and ABX audio testing. Validates randomization, calculates statistical significance, and ensures proper experimental design. Use when implementing A/B test features or analyzing test results.

a-b-testing

16
from diegosouzapw/awesome-omni-skill

The science of learning through controlled experimentation. A/B testing isn't about picking winners—it's about building a culture of validated learning and reducing the cost of being wrong. This skill covers experiment design, statistical rigor, feature flagging, analysis, and building experimentation into product development. The best experimenters know that every test, positive or negative, teaches something valuable. Use when "a/b test, experiment, hypothesis, statistical significance, sample size, feature flag, variant, control, treatment, p-value, conversion rate, test winner, split test, experimentation, testing, statistics, feature-flags, hypothesis, growth, optimization, learning, validation" mentioned.

web-testing

16
from diegosouzapw/awesome-omni-skill

Playwright automation, Chrome DevTools debugging, and browser interaction testing. Use for E2E/unit tests, capturing screenshots, inspecting network/console logs, or validating user flows in web applications.

qa-testing-mobile

16
from diegosouzapw/awesome-omni-skill

Mobile app testing strategy and execution for iOS and Android (native + cross-platform): choose automation frameworks, define device matrix, control flakes, validate performance/reliability/accessibility, and set CI + release gates. Use when you need a mobile QA plan, device lab/CI setup, or guidance on XCUITest/Espresso/Appium/Detox/Maestro/Flutter testing.

anthropic-webapp-testing

16
from diegosouzapw/awesome-omni-skill

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

anthropic-web-testing

16
from diegosouzapw/awesome-omni-skill

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Frontend Verification & Testing

16
from diegosouzapw/awesome-omni-skill

Verify and test Angular 18 frontend changes using Chrome DevTools MCP. Automatically check console errors, network requests, and visual rendering after implementing tasks or when fixing UI bugs. Use when creating components, debugging visual issues, validating API integration, or ensuring UI requirements are met. File types: .ts, .html, .css, .scss

frontend-react-testing-strategy

16
from diegosouzapw/awesome-omni-skill

Standardized guidelines and patterns for Frontend React Testing Strategy.

angular-testing

16
from diegosouzapw/awesome-omni-skill

Write unit and integration tests for Angular v21+ applications using Vitest or Jasmine with TestBed, component harnesses, and modern testing patterns. Use for testing components with signals, OnPush change detection, services with inject(), and HTTP interactions. Triggers on test creation, testing signal-based components, mocking dependencies, or setting up test infrastructure.

testing-automation

16
from diegosouzapw/awesome-omni-skill

Automated testing workflow that orchestrates unit, integration, and E2E tests with CI/CD integration

continuous-testing

16
from diegosouzapw/awesome-omni-skill

Integrate automated testing into CI/CD pipelines for continuous quality feedback. Use for continuous testing, CI testing, automated testing pipelines, test orchestration, and DevOps quality practices.

cloud-penetration-testing

16
from diegosouzapw/awesome-omni-skill

This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfiguratio...