Skip to content
TrustedSkillsbeta
Back to all skills

Content Experimentation Best Practices

Official
sanity-io·vlatest·testing·MIT

Optimize content performance using Sanity's best practices for A/B testing, personalization, and data-driven iteration.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add sanity-io/agent-toolkit --skill content-experimentation-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

sanity-io

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned sanity-io/agent-toolkit at 88d6cdfa7c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
88d6cdfa7c
Manifest
skills/content-experimentation-best-practices/SKILL.md
Scanned
5 files, 731 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidance on best practices for conducting content experiments, helping users design, execute, and analyze tests to optimize content performance. It includes strategies for hypothesis formation, A/B testing, data interpretation, and iterative improvement.

When to use it

  • When launching a new content campaign and wanting structured methods to test different approaches.
  • When analyzing underperforming content and seeking actionable insights for improvement.
  • When looking to refine messaging or formatting based on audience engagement metrics.
  • When preparing to scale content efforts with data-driven decisions.

Key capabilities

  • Guidance on forming clear hypotheses before testing.
  • Techniques for setting up A/B tests effectively.
  • Methods for measuring success and interpreting results.
  • Recommendations for iterating based on experiment outcomes.

Example prompts

  • "How should I structure an A/B test for my blog headlines?"
  • "What metrics should I track to evaluate the success of a content experiment?"
  • "Can you provide best practices for analyzing user engagement data from content tests?"

Tips & gotchas

  • Ensure your experiments are based on clear objectives and measurable outcomes.
  • Avoid testing too many variables at once, as it can complicate result interpretation.