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

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

An exemplary compact skill body: lean, concrete, and structured with a strong validate-then-deploy workflow and an explicit error-recovery loop. The only minor gap is the absence of an example GROQ query to make the GROQ guidance fully copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and efficient: short sectioned rules with no padding, no explanation of what a CMS or GROQ is, and every line earns its place, matching the top anchor.

5 / 5

Actionability

Concrete, executable guidance throughout (get_schema, author-> vs author[]->, drafts. prefix, defineType/defineField, sanity dataset export/import, sanity start), with the minor gap of no example GROQ query snippet, placing it just below copy-paste-ready 5.

4 / 5

Workflow Clarity

The 'Change -> validate -> deploy' section is a clear numbered sequence with explicit validation checkpoints (sanity start surfaces errors, Vision queries, temp-dataset import, full site build) and a feedback loop ('Any failure: revert locally, fix, restart from step 1'), matching the top anchor for a destructive/batch workflow.

5 / 5

Progressive Disclosure

A short, well-sectioned overview with a single clearly signaled one-level reference (sanity-config.md) plus a docs link; content is appropriately split and easy to navigate, fitting the top anchor for a compact skill.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description that clearly states capabilities and provides explicit, natural trigger guidance for the Sanity CMS domain. Minor specificity and synonym coverage gaps keep it just short of perfect on two dimensions.

DimensionReasoningScore

Specificity

Lists several concrete actions (manages schemas, GROQ queries, dataset exports/imports, Studio configuration) with only minor coverage gaps such as migrations/plugins, fitting the 'several specific actions' anchor rather than the fully comprehensive 5.

4 / 5

Completeness

Explicitly answers both what ('Manages Sanity CMS schemas, GROQ queries, dataset exports/imports, and Studio configuration') and when ('Use when...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural trigger terms ('updating Sanity schemas', 'running GROQ or Vision queries', 'exporting datasets', 'modifying content models', 'headless CMS', 'Sanity.io') that users would actually say, with only a few synonyms missing, so it sits above the midpoint but short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear Sanity CMS niche with product-specific triggers (GROQ, Vision, Sanity.io) makes overlap with other skills minimal, matching the distinct-triggers anchor.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.