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.
Install
/plugin marketplace add sanity-io/agent-toolkitThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sanity-io/agent-toolkit --skill content-experimentation-best-practicesgit clone --depth 1 https://github.com/sanity-io/agent-toolkit.git /tmp/agent-toolkit
mkdir -p ~/.claude/skills
cp -r /tmp/agent-toolkit/skills/content-experimentation-best-practices ~/.claude/skills/content-experimentation-best-practicesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the 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). ## 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
Details
- Skill name
content-experimentation-best-practices- Repository
- sanity-io/agent-toolkit
- Path
skills/content-experimentation-best-practices/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Content Experimentation Best Practices skill do?
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.
How do I install the Content Experimentation Best Practices skill?
Claude Code plugin: /plugin marketplace add sanity-io/agent-toolkit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Content Experimentation Best Practices popular?
It lives in sanity-io/agent-toolkit, which has 200 GitHub stars and 32 forks, and is included in 1 curated skill list.
Related skills
Content Modeling Best Practices
200sanity-io/agent-toolkit
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.
Portable Text Conversion
200sanity-io/agent-toolkit
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.
Portable Text Serialization
200sanity-io/agent-toolkit
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.
Spec
434owainlewis/blueprint
Writes a spec for one feature: a short PRD (problem and user journeys) plus the technical design an agent builds from. Use when decisions must be settled before building. The spec is the ticket.
Requirements
434owainlewis/blueprint
Writes the product requirements document (PRD) in root REQUIREMENTS.md as user stories with checkable outcomes. Use for a new product or a change to what it should do.
Cinema Manager
276DavidBB-L/cinema-manager
Personal media library management — discover content, save to Quark cloud drive, auto-organize for Infuse/Plex. Plugin system for content sources. Use when user wants to find/watch movies, save to cloud drive, or manage media library.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.