Some SanityPress instances define custom skill documents (_type: 'skill', schema at src/sanity/schemaTypes/documents/skill.ts, Studio nav "Skills") — free-form agent guidance authored as Studio content rather than a repo file. Each has name (slug), title, description, and content (a code field, markdown). Because it lives in the dataset, not the codebase, it never appears in .agents/skills/, .claude/skills/, or any file-based skill listing — the only way to find it is to query for it.

Step 1 — Query for skill documents

Before writing original prose for a SanityPress instance (page copy, blog posts, CTA labels, metadata titles/descriptions), query:

*[_type == "skill"]{ "name": name.current, title, description }

Use query_documents against the target project/dataset. If it returns nothing, stop here — there's nothing to apply, proceed with the task normally.

Step 2 — Judge relevance

Judge each result's relevance to the current task from its title/description alone (don't fetch content yet):

check-studio-skills

Step 1 — Query for skill documents

Step 2 — Judge relevance