Conciseness

The body is mostly efficient and assumes competence, but there is noticeable repetition: the freshness hierarchy appears in full in step 2 ("(a) if a served docs tool... (b) else fetch the specific docs page... (c) only then fall back") and again as a Rules bullet ("Follow the freshness hierarchy: served docs tool → page-as-markdown / pinned README → general web"), and "never write from memory" is stated three times (intro, step 2's "Do NOT skip to writing the API from memory", and Rules bullet 1). The intro also pads with narrative ("excellent for stable idioms, but it goes stale exactly where it hurts"). This fits the 3 anchor — could be tightened — better than the 4 anchor's "minor instances".

Actionability

Concrete, executable guidance is present: a runnable version-pinning command ("node -p \"require('./node_modules/convex/package.json').version\""), a named MCP tool ("search_convex_docs"), a concrete URL pattern ("docs.convex.dev/<path>"), and a ground-truth check path ("node_modules/@convex-dev/<x>/" ... "its package.json exports, its .d.ts"). It is not a 5 because the actual fetch step (b) has no executable example — no curl/WebFetch command or worked URL — leaving a minor gap.

Workflow Clarity

The 5-step sequence is clearly ordered with an explicit verification checkpoint (step 3, "VERIFY against the installed package") and a genuine error-recovery feedback loop (step 5, "On a version-mismatch build error... treat it as a currentness question — pin the version, fetch the current API, and correct"). This matches the 5 anchor's "clear sequence with explicit validation steps; feedback loops for error recovery"; operations here are read-only, so the destructive/batch cap does not apply.

Progressive Disclosure

The skill is under 50 lines, single-purpose, and has no bundle files (no references/, scripts/, or assets/ exist), and the body makes no dangling file references — every pointer is to an external site or a sibling skill, which keeps content one level deep. Per the simple-skill exception, the well-organized Workflow/Rules sectioning earns the 5 anchor.

Specificity

The description lists several concrete actions — "pin the installed version", "fetch page-as-markdown", "check node_modules types" — anchored to a named domain ("version-current Convex docs"). It falls short of the 5 anchor because "freshness hierarchy" is named as a capability but never unpacked, leaving a minor gap in coverage.

Completeness

The 'what' is explicit and multi-part ("pin the installed version, fetch page-as-markdown or check node_modules types"), and the 'when' is present as an explicit trigger contrast — "instead of writing a possibly-stale API from memory" — which clearly names the triggering situation. It is not a 5 because the trigger is phrased as a negative contrast rather than a direct 'Use when...' clause with concrete trigger phrases; not a 3 because the when-guidance is explicit, not merely implied.

Trigger Term Quality

Natural phrases a user would say are present — "Pull version-current Convex docs", "pin the installed version", "stale API from memory" — plus the domain keyword "Convex". A few natural variants are missing (e.g., "Convex documentation", "up-to-date API reference", "@convex-dev"), so it does not reach the comprehensive synonym/extension coverage of the 5 anchor.

Distinctiveness Conflict Risk

The niche is precise — version-pinned Convex documentation retrieval — with distinct triggers ("Convex docs", "pin the installed version") that would not naturally fire for other skills. This matches the 5 anchor's "clear niche with distinct triggers; minimal conflict risk"; the only adjacency is the sibling convex-expert skill, which the description does not overlap with.