Labsco
Labsco/Repos/sanity-io/agent-toolkit
REPO PACKAGE

sanity-io agent-toolkit

COMMUNITY
sanity-io · publisher188 repository starsMIT · Freegithub.com/sanity-io/agent-toolkit
8skills
3groups
6ready to use

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.

8Grouped into 3 sets by the authors.
6Work with nothing else to set up.
188Stars on the GitHub repository, at last check.