content-experimentation-best-practices
Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or building experimentation workflows in a CMS or frontend stack.
Works with
--- name: content-experimentation-best-practices description: Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or building experimentation workflows in a CMS or frontend stack. license: MIT --- # Content Experimentation Best Practices Principles and patterns for running effective content experiments to improve conversion rates, engagement, and user experience. ## When to Apply Reference these guidelines when: - Setting up A/B or multivariate testing infrastructure - Designing experiments for content changes - Analyzing and interpreting test results - Building CMS integrations for experimentation - Deciding what to test and how ## Core Concepts ### A/B Testing Comparing two variants (A vs B) to determine which performs better. ### Multivariate Testing Testing multiple variables simultaneously to find optimal combinations. ### Statistical Significance The confidence level that results aren't due to random chance. ### Experimentation Culture Making decisions based on data rather than opinions (HiPPO avoidance). ## References Start with the reference that matches the current problem, such as design, statistics, CMS integration, or pitfalls. See `references/` for detailed guidance: - `references/experiment-design.md` — Hypothesis framework, metrics, sample size, and what to test - `references/statistical-foundations.md` — p-values, confidence intervals, power analysis, Bayesian methods - `references/cms-integration.md` — CMS-managed variants, field-level variants, external platforms - `references/common-pitfalls.md` — 17 common mistakes across statistics, design, execution, and interpretation
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

