sanity-cms
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.
100
100%
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 its scope within the Sanity CMS ecosystem. It lists concrete actions, includes rich trigger terms that users would naturally use, and has an explicit 'Use when...' clause. The Sanity-specific terminology makes it highly distinctive and unlikely to conflict with other skills.
| 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 natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific Sanity CMS ecosystem focus, including Sanity-specific terms like GROQ, Vision queries, and Studio. Very unlikely to conflict with other CMS or general content management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that is concise, actionable, and well-structured. It provides executable examples for both GROQ queries and schema definitions, includes a clear multi-step workflow with validation checkpoints and error recovery, and appropriately delegates project-specific details to a separate file. The critical development rules are practical and address real pitfalls (silent failures from array vs single reference, draft prefix handling).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Sanity CMS is or how GROQ works conceptually—it jumps straight into actionable rules, examples, and workflows. Every section earns its place. | 3 / 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 (Vision queries, dataset export/import into temporary dataset, end-to-end builds) and includes a feedback loop (step 5: revert, fix, repeat from step 1). | 3 / 3 |
Progressive Disclosure | The skill serves as a concise overview and immediately points to the project-specific configuration file (sanity-config.md) for customization. Content is well-organized into distinct sections without being monolithic or deeply nested. | 3 / 3 |
Total | 12 / 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.
- Repository
- monkilabs/opencastle
- Commit
f5c8508
- Reviewed
Table of Contents
Is this your skill?
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.