How do I install the Ab Testing skill?

Run npx skillmds@latest add tomevault-io/ab-testing-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ab Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ab Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ab Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ab Testing?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ab Testing by tomevault-io — Agent Skill

Name: Ab Testing
Author: tomevault-io

Ab Testing

Production A/B testing lifecycle for design variants. Covers hypothesis formation, feature flags, variant comparison, analytics tracking, statistical significance analysis, experiment setup, and cleanup. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

A/B Testing

This skill provides the complete lifecycle for production A/B testing of design variants. Variants are real, production-quality code — not mockups.

Lifecycle

CREATE (/design) → DEPLOY (trunk + flags) → MEASURE (analytics) → DECIDE (/ab-decide) → CLEANUP (/ab-cleanup)

1. CREATE

/blueprint-dev:bp:design uses the design-variant-generator to create 2-3 real component variants, the design-critic to evaluate them, and the ab-test-engineer to wire up flags and tracking.

2. DEPLOY

Variants ship to trunk behind feature flags. Compatible with trunk-based development — no long-lived branches needed.

3. MEASURE

Analytics tracking fires at key interaction points. Users monitor their analytics dashboard for results.

4. DECIDE

/blueprint-dev:bp:ab-decide uses the design-decision-analyst to interpret results and recommend a winner based on statistical significance.

5. CLEANUP

/blueprint-dev:bp:ab-cleanup follows the decision document's cleanup plan to remove the losing variant, promote the winner, and clean up flags/tracking.

Key Principles

Meaningful differences: Variants must differ in layout, interaction, hierarchy, density, or navigation — not just cosmetics
Statistical rigor: p < 0.05, 80% power, calculated sample sizes
Guardrail metrics: Tests auto-stop if critical metrics degrade
Clean cleanup: Every test ends with a clean codebase — no lingering dead code

References

references/tracking-plan-template.md — Template for tracking plans
references/code-templates.md — Stack-specific code templates for wrappers, flags, and tracking

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: ab-testing-2description: Production A/B testing lifecycle for design variants. Covers hypothesis formation, feature flags, variant comparison, analytics tracking, statistical significance analysis, experiment setup, and cleanup. Use when this capability is needed.---# A/B TestingThis skill provides the complete lifecycle for production A/B testing of design variants. Variants are real, production-quality code — not mockups.## Lifecycle```CREATE (/design) → DEPLOY (trunk + flags) → MEASURE (analytics) → DECIDE (/ab-decide) → CLEANUP (/ab-cleanup)```### 1. CREATE`/blueprint-dev:bp:design` uses the design-variant-generator to create 2-3 real component variants, the design-critic to evaluate them, and the ab-test-engineer to wire up flags and tracking.### 2. DEPLOYVariants ship to trunk behind feature flags. Compatible with trunk-based development — no long-lived branches needed.### 3. MEASUREAnalytics tracking fires at key interaction points. Users monitor their analytics dashboard for results.### 4. DECIDE`/blueprint-dev:bp:ab-decide` uses the design-decision-analyst to interpret results and recommend a winner based on statistical significance.### 5. CLEANUP`/blueprint-dev:bp:ab-cleanup` follows the decision document's cleanup plan to remove the losing variant, promote the winner, and clean up flags/tracking.## Key Principles- **Meaningful differences**: Variants must differ in layout, interaction, hierarchy, density, or navigation — not just cosmetics- **Statistical rigor**: p < 0.05, 80% power, calculated sample sizes- **Guardrail metrics**: Tests auto-stop if critical metrics degrade- **Clean cleanup**: Every test ends with a clean codebase — no lingering dead code## References- `references/tracking-plan-template.md` — Template for tracking plans- `references/code-templates.md` — Stack-specific code templates for wrappers, flags, and tracking---> Converted and distributed by [TomeVault](https://tomevault.io/claim/dlabs) — claim your Tome and manage your conversions.

Frequently asked questions