sanity-io agent-toolkit
COMMUNITYLABSCO SUMMARY
The biggest of the seven, sanity-best-practices, covers GROQ queries, schema design with defineType/defineField, TypeGen, Visual Editing, images, Studio structure, localization, Sanity Functions, webhooks, and framework integration for Next.js, Nuxt, Astro, Remix, SvelteKit, and more. The other six are narrower: content-modeling-best-practices argues references versus embedded objects and reusable versus page-shaped schemas; portable-text-conversion turns HTML or Markdown into Portable Text blocks; portable-text-serialization renders Portable Text back out to React, Svelte, Vue, Astro, HTML, Markdown, or plain text; sanity-migration plans and reviews a move from Contentful, WordPress, Webflow, Drupal, AEM, Strapi, Payload, or raw exports; seo-aeo-best-practices covers metadata, Open Graph, sitemaps, hreflang, and JSON-LD for both search engines and AI answer surfaces; and content-experimentation-best-practices covers A/B test design, sample size, and statistics for CMS-managed variants.
This is for teams already building on, or actively migrating onto, Sanity — the skills assume Sanity's own schema and query language throughout, down to the SEO one, which frames its structured-data advice around a Sanity-backed frontend rather than CMS-agnostic guidance.
READ THE FULL ANALYSIS
The skills are the fallback path, not the lead. Sanity's own README puts a hosted MCP server (https://mcp.sanity.io) first, giving an agent live read/write access to a project's content, schema, and Studio deploys with no local files to maintain; the seven skills are "Option 2" for MCP-incompatible clients or as an add-on alongside it, and a third path bundles both into a Claude Code or Cursor plugin.
One skill assumes real tooling, not just chat. sanity-migration is the one our check flags as needing a local tool rather than pure guidance — moving real content off another CMS means running actual extraction and Portable Text conversion scripts against the source system, not just reading advice.
Nothing here is useful without Sanity. If you are on a different headless CMS and have no plans to move, none of the seven skills apply as written — they teach Sanity's own APIs and conventions throughout, not general content-modeling theory.
ALSO IN THIS PACKAGE
sanity
Sanity plugin for Claude Code with MCP server, agent skills, agent rules, and slash commands.
Sanity
Direct access to your Sanity projects (content, datasets, releases, schemas) and agent rules
http · https://mcp.sanity.ioWHAT'S INSIDE
8 showing · 8 totalNothing else to set up — install it and go.
content-experimentation-best-practices
Running an A/B test on website content properly: choosing what to measure, running it long enough for the answer to mean anything, and not being fooled by a result that was really chance.
sanity-studio-upgrade
Writes an upgrade plan for the Sanity Studio in your repository that lists only the changes that apply to your project, plus the questions only a person can answer, without touching any of your code.
seo-aeo-best-practices
Getting a page found twice over: ranked in Google's results the ordinary way, and picked as the answer when someone asks an AI assistant instead.
portable-text-conversion
Sanity stores articles in its own format rather than as HTML, so content arriving from an older site has to be translated first — this is that translation, from HTML or Markdown.
portable-text-serialization
Text stored in Sanity has to be turned back into something a browser can show; this covers doing that in React, Svelte, Vue or Astro, and converting it to HTML, Markdown or plain text.
sanity-migration
Moving a site's content out of an old content system and into Sanity, planned the way a real project is rather than copied across by hand.
content-modeling-best-practices
How to organise the text and images in a content system so they can be reused on a new page, app or channel later, rather than being shaped to fit the one screen they were written for.
sanity-best-practices
Sanity's own engineers wrote down how they want a Sanity project built, and this is that advice — the content structure, the queries, the frontend wiring and the editing experience.
HOW TO GET IT
npx skills add sanity-io/agent-toolkitnpx skills add sanity-io/agent-toolkit --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.
/plugin marketplace add sanity-io/agent-toolkit/plugin install sanity@sanity-agent-toolkitTyped inside the agent's own prompt, not in a terminal. The marketplace is called sanity-agent-toolkit, which is the part after the @.