Manages Sanity CMS schemas, GROQ queries, dataset exports/imports, and Studio configuration. Use when updating Sanity schemas, running GROQ or Vision queries, exporting datasets, modifying content models, or configuring a headless CMS with Sanity.io.
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines specific capabilities within the Sanity CMS ecosystem, includes a comprehensive 'Use when...' clause with natural trigger terms, and is highly distinctive due to its focus on a specific product and its proprietary technologies like GROQ. It follows all best practices including third-person voice and concise yet comprehensive coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: managing schemas, GROQ queries, dataset exports/imports, and Studio configuration. These are distinct, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (manages schemas, GROQ queries, dataset exports/imports, Studio configuration) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Sanity CMS', 'schemas', 'GROQ', 'Vision queries', 'dataset exports', 'content models', 'headless CMS', 'Sanity.io', and 'Studio configuration'. Good coverage of both technical terms and common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific focus on Sanity CMS, GROQ queries, and Sanity.io ecosystem. Very unlikely to conflict with other CMS skills given the named product and proprietary query language. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that provides concrete, actionable guidance for Sanity CMS development. The GROQ examples and schema definition are executable and copy-paste ready, and the workflow includes proper validation checkpoints with a feedback loop. Minor verbosity in the critical rules section prevents a perfect conciseness score, but overall the content is efficient and well-organized.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but some rules are somewhat verbose (e.g., rule 5 'validate queries against real data in the Vision plugin before deploying' could be tighter). The explanatory clauses after each rule add mild padding, though the overall content is reasonably lean. | 2 / 3 |
Actionability | Provides fully executable GROQ query examples and a complete, copy-paste-ready schema definition using defineType/defineField. The CLI commands (sanity start, sanity dataset export/import) are specific and concrete. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit validation checkpoints at multiple stages (local schema errors, Vision queries, staging dataset import, end-to-end builds) and includes a feedback loop (step 5: revert, fix, repeat from step 1). | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with a clear one-level-deep reference to project-specific configuration in sanity-config.md. Content is well-organized into distinct sections (rules, examples, schema, workflow) without being monolithic. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
18c6f2c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.