Agent skill
content-experimentation-best-practices
A/B testing and content experimentation methodology for data-driven optimization. Use when setting up A/B tests, multivariate tests, or experimentation infrastructure — including experiment design, statistical significance, conversion rate optimization (CRO), feature flags, or integrating experiments with a CMS. Trigger when the user mentions A/B test, split test, variant, experiment, CRO, conversion rate, statistical significance, feature flag, or asks how to test or measure content changes.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/content-experimentation-best-practices
Metadata
Additional technical details for this skill
- author
- sanity
- version
- 1.0.0
SKILL.md
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).
Resources
See resources/ for detailed guidance:
- Experiment design principles
- Statistical foundations
- CMS integration patterns
- Common pitfalls
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?