sanity-cms

Validate GROQ queries and schema edits for Sanity CMS projects.

59|12|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/etylsarin/opencastle --skill sanity-cms-etylsarin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sanity-cms
Source: https://github.com/etylsarin/opencastle/tree/main/src/orchestrator/plugins/sanity
Command: npx skills add https://github.com/etylsarin/opencastle --skill sanity-cms-etylsarin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sanity projects commonly encounter silent failures from incorrect GROQ queries, schema mismatches, and improper handling of drafts or reference cardinality, causing broken content and deployment regressions.

Core Features & Use Cases

  • Schema-first validation: Emphasizes checking local Studio schema files before writing queries or making schema changes to avoid drift.
  • GROQ query guidance: Provides patterns and best practices for writing and testing GROQ, including Vision testing and shared query libraries.
  • Content workflow safety: Covers draft/publish handling, array vs single-reference pitfalls, and recommended deploy and migration patterns for content engineers and copywriters.

Quick Start

Use the sanity-cms skill to inspect the project's schema, validate a GROQ query in Vision, and highlight any mismatched fields before deployment.

Frequently Asked Questions about sanity-cms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate GROQ queries against my Sanity schema before deploying?

To validate GROQ queries against your Sanity schema, inspect local Studio schema files first, then test queries using Vision to highlight mismatched fields and prevent silent deployment failures.

Why does my Sanity GROQ query return silent failures or broken content?

Sanity GROQ queries return silent failures when there are schema mismatches or incorrect query syntax. Checking local Studio schema files before writing queries prevents drift and avoids broken content.

What is the best way to handle draft and publish patterns in a Sanity CMS?

Handling draft and publish patterns in Sanity CMS requires schema-first validation to manage content workflow safety. This approach prevents regressions by ensuring proper reference cardinality and avoiding array versus single-reference pitfalls.

Do I need local Studio schema files and Sanity API credentials to inspect content models?

Yes, inspecting Sanity content models and validating schema changes requires access to local Studio schema files and Sanity API credentials to ensure accurate guidance and prevent content deployment regressions.

How do I prevent schema drift when making content model changes in Sanity?

Preventing schema drift during Sanity content model changes involves validating local Studio schema files before applying edits. This schema-first approach ensures GROQ queries and references remain aligned with the updated model.