cms

Headless CMS integration guidance — Sanity (native Vercel Marketplace), Contentful, DatoCMS, Storyblok, and Builder.io. Covers studio setup, content modeling, preview mode, revalidation webhooks, and Visual Editing. Use when building content-driven sites with a headless CMS on Vercel.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

65%

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

A highly actionable, code-rich reference with clean sectioning, weakened mainly by inline version-sensitive guidance and a single-file structure that inlines content that could be split into bundle references.

Suggestions

Move version-sensitive guidance (apiVersion, next-sanity v11→v12 migration notes, Studio v5+/React 19.2 requirements) into a dedicated 'Version notes' or 'Deprecated patterns' section so it does not penalize the main content.

Add an explicit ordered integration workflow (e.g., 1. install via Marketplace, 2. configure client, 3. define schema, 4. embed studio, 5. enable Visual Editing, 6. wire revalidation webhook) with validation checkpoints between steps.

Split per-CMS detail into one-level-deep reference files (e.g., references/sanity.md, references/contentful.md) and cover DatoCMS, Storyblok, and Builder.io beyond the env-var table, keeping SKILL.md an overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with brief lead-ins and does not explain concepts Claude already knows, but time-sensitive version/date info (apiVersion "2026-03-01", next-sanity v12/v11+, Studio v5+ / React 19.2) is scattered inline rather than confined to a deprecated/old-patterns section.	2 / 3
Actionability	Provides fully executable install commands and complete TypeScript for client config, schema definition, embedded studio, defineLive, VisualEditing, the revalidation webhook, Contentful fetching, and the draft-mode route, with file paths noted in comments.	3 / 3
Workflow Clarity	Sections are implicitly ordered (install → client → schema → studio → live → visual editing → webhook) and individual endpoints validate secrets/signatures, but there is no explicit sequenced integration workflow with connecting validation checkpoints across the steps.	2 / 3
Progressive Disclosure	The ~280-line body is well-sectioned by headers but inlines per-CMS detail (and unevenly covers the five named platforms) into a single file with no one-level-deep bundle references to split out deeper material.	2 / 3
	Total	9 / 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.

A strong description that names concrete capabilities, lists the supported platforms, and provides an explicit "Use when" trigger with a clear Vercel/headless-CMS niche. It avoids verbosity and second-person voice.

Dimension	Reasoning	Score
Specificity	"Covers studio setup, content modeling, preview mode, revalidation webhooks, and Visual Editing" lists multiple concrete capabilities rather than vague language, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly states both what it does (integration guidance across the listed capabilities) and when to use it via "Use when building content-driven sites with a headless CMS on Vercel."	3 / 3
Trigger Term Quality	Includes natural terms users would say — "headless CMS", named platforms (Sanity, Contentful, DatoCMS, Storyblok, Builder.io), "preview mode", "revalidation webhooks" — giving good coverage of likely user phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to headless CMS integration on Vercel with five named platforms, giving it a clear niche with distinct triggers unlikely to collide with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: openai/plugins
Path: plugins/vercel/skills/cms/SKILL.md
Commit: 11c74d6

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.