Content
78%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong, highly executable reference with excellent code examples and built-in auth validation on webhook and draft routes. Its main gaps are duplication and time-sensitive version details that could be tightened, and the absence of any progressive-disclosure structure for the substantial Sanity material.
Suggestions
Move the Sanity deep-dive (studio setup, defineLive, Visual Editing) into a references/sanity.md file and keep a concise overview in SKILL.md, applying the same pattern for other platforms to even out coverage.
De-duplicate the createClient config block by showing it once and referencing it from the defineLive section.
Collect version-sensitive notes (v11/v12 breaking changes, React 19.2, apiVersion pinning) into a clearly labeled migration/deprecation section so they don't read as inline current-state noise.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and executable with almost no concept explanation, but the createClient config appears twice (plain and in the defineLive section), a pinned apiVersion date ("2026-03-01") is inlined in code, and framing sentences like "Sanity is the primary CMS integration on the Vercel Marketplace..." could be trimmed. Efficient with minor instances of over-explanation, matching the 4 anchor rather than the every-token-earns-its-place anchor at 5. | 4 / 5 |
Actionability | Fully copy-paste-ready guidance throughout: install commands, client config, content schema, embedded studio, defineLive usage, Visual Editing setup, a signature-validated revalidation webhook, a draft-mode route, an env-var table, and official doc links. Covers the common cases for every listed platform except the thinly-treated DatoCMS/Storyblok/Builder.io, which still get concrete env vars or install patterns. | 5 / 5 |
Workflow Clarity | Sections follow a coherent install → configure → fetch → preview → revalidate sequence, and the risky routes include explicit auth checkpoints (401 on invalid webhook signature or draft secret). Falls short of 5 because there is no numbered integration sequence or verify/recovery loop, and short of 3 because validation is present where it matters most. | 4 / 5 |
Progressive Disclosure | No bundle files exist, so everything is inlined in SKILL.md. Section structure is clear, but the ~180-line Sanity deep-dive (studio, live content, visual editing) is content that belongs in a separate reference file, coverage across the five platforms is uneven, and cross-references use a "⤳ skill:" notation rather than resolvable links — matching the 3 anchor (good structure, but content that should be separate is inline). | 3 / 5 |
Total | 16 / 20 Passed |