Sanity CMS Operator

What this skill does

Sanity CMS Operator skill guides content operations in Sanity.io: schema-aware document creation and updates, GROQ query drafting, portable text editing patterns, asset management, slug and SEO field hygiene, reference linking between content types, and publish workflow coordination for marketing sites using Sanity as headless CMS—including Metaflow's own marketing properties.

It helps practitioners interact with structured content models without breaking validation rules, and produces change specs developers can implement when schema extensions are needed.

Who it's for

Content marketers publishing blog, skills, landing pages, and changelog entries; SEO teams updating metadata at scale; and growth engineers bridging Sanity Studio operations with Next.js frontends. Useful when non-developers need reliable CMS assistance aligned to project schemas.

Key workflows

Identify document type and required fields from schema context. Draft or revise content with proper portable text structure, internal references, categories, and SEO components. Propose GROQ queries for fetching related content or validating orphaned documents.

Bulk update patterns for metadata refreshes, redirect notes when slugs change, and preview checklist before publish. Coordinate with SEO skills for on-page fields and sitemap implications.

Common questions

Editors ask Studio versus API updates—Operator focuses on safe editorial workflows within defined schemas. Another topic is portable text custom blocks; guidance respects existing block types without inventing unsupported structures.

Localization and multi-market content get field-level notes when schema supports i18n.

How to use in Metaflow

Attach when tasks involve Sanity content for metaflow.life or your Sanity project. Provide document type, slug, or paste existing JSON/portable text. Request drafts, GROQ, or publish checklists. Pair with On-Page SEO skill for metadata on new URLs and Artifact Composer for preview content reviews.

Editorial workflows cover draft versus published states, preview URL validation, and reference integrity when deleting linked documents breaks page builds. SEO field updates sync with sitemap and internal link expectations—slug changes trigger redirect planning conversations. Asset pipeline guidance includes alt text, focal point crops, and file size norms for Core Web Vitals on content-heavy pages. When schema in Sanity drives frontend components, Operator respects required blocks and validation messages rather than inventing unsupported content structures.

Bulk metadata update patterns help SEO teams refresh title and description templates across document sets without manual Studio clicking. Webhook and ISR implications are flagged when publishing triggers frontend rebuilds—coord timing with devs prevents partial deploys during large content launches.

Content model extension requests include schema change specs developers can implement—new fields, validation rules, and Studio preview updates—without breaking existing published documents.

For broader context, see our roundup of claude skills for marketing, and read how to create Claude skills for related setup guidance.