CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, well-structured Sanity CMS skill with executable examples, clear workflow steps, and proper validation checkpoints. Its main strengths are actionability (concrete GROQ queries, schema code, CLI commands) and workflow clarity with explicit feedback loops. Minor weaknesses include slightly verbose critical rules and the inability to verify the referenced sanity-config.md file.

DimensionReasoningScore

Conciseness

Mostly efficient but some rules are somewhat verbose (e.g., rule 7 'queries belong in a shared queries library, never inline in components' could be tighter). The critical rules section has some padding, but overall the skill doesn't over-explain concepts Claude already knows.

2 / 3

Actionability

Provides fully executable GROQ query examples and a complete, copy-paste-ready schema definition using defineType/defineField. Concrete CLI commands (sanity start, sanity dataset export/import) are specified for the workflow steps.

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 in step 5 for error recovery (revert, fix, repeat from step 1).

3 / 3

Progressive Disclosure

References project-specific config in sanity-config.md which is good, but no bundle files are provided to verify that reference. The skill is reasonably structured with sections, but the critical rules section is fairly long and could potentially be split out for a cleaner overview.

2 / 3

Total

10

/

12

Passed

Description

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 a well-crafted skill description that clearly identifies the specific CMS platform (Sanity), lists concrete capabilities, and provides explicit trigger guidance. It uses third-person voice correctly and includes both domain-specific terms (GROQ, Vision queries) and broader terms (headless CMS, content models) that users might naturally use.

DimensionReasoningScore

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 technology focus on Sanity CMS, GROQ queries, and Sanity.io. Very unlikely to conflict with other CMS skills given the explicit naming of the platform and its unique query language.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.