content-experimentation-best-practices
Content A/B testing and experimentation workflows
Developer Setup
Setup & Installation
npx skills add https://github.com/sanity-io/agent-toolkit --skill content-experimentation-best-practicesnpx skills add https://github.com/sanity-io/agent-toolkit --skill content-experimentation-best-practicesOverview
What This Skill Does
Covers experiment design, statistical analysis, and CMS-managed variant setup for content A/B and multivariate testing. Includes hypothesis frameworks, sample size calculation, p-values, confidence intervals, and a catalog of 17 common pitfalls across design, execution, and interpretation. Addresses both the statistics layer and the CMS integration layer.
Application
When to use this Skill
- Configuring integration settings for custom agent workflows.
- Optimizing query execution and response latency in production.
- Developing clean, standard-compliant implementations for enterprise services.
- Troubleshooting connection timeouts and authentication handshakes.
- Monitoring API rate limits and execution pipelines programmatically.
Documentation
Show Skills.md file
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
Recommendations
Explore other random skills
chdb-sql
>-
clickhouse-architecture-advisor
MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.
clickhouse-best-practices
MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 31 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.