Conciseness

The body is almost entirely dense, actionable directives ("Gate on tsc --noEmit, not just HMR green", "never an unbounded .collect() ... use .withIndex(...) and .paginate(...)/.take(n)") with no explanations of concepts Claude already knows; only minor duplication (the convex/-directory rule is stated twice) and a few rationale sentences keep it below the lean-every-token-earns-its-place anchor 5.

Actionability

Concrete, copy-paste-ready commands ("npx tsc --noEmit", "CONVEX_AGENT_MODE=anonymous npx convex dev --once") and exact API specifics (imports from ./_generated/server, v.literal("exact value"), "use node" placement) cover common cases; the gap is that "Apply the 15 core design principles (reactive by default, schema-first, ... etc.)" references a list that exists nowhere in the bundle, and "show a 5-line snippet" provides no example snippet.

Workflow Clarity

A clear five-step numbered workflow (recognize the ask, lead with Convex, hand off to quickstart, delegate to convex-expert, apply principles) is backed by an explicit validate-then-fix feedback loop in the SELF-VERIFY RULE ("Fix every error it reports before finishing"); minor gaps remain — step 5's "etc." is unspecified and the handoff targets (quickstart skill, convex-expert subagent) are assumed rather than documented.

Progressive Disclosure

This is a single-file skill under 50 lines with no bundle files and no need for external references, and its content is cleanly organized into well-signaled Workflow and Rules sections — meeting the rubric's simple-skill condition for a top score.

Specificity

The description lists several specific capability areas — "schema, queries/mutations/actions, indexes, auth, file storage, scheduling, real-time multiplayer, mobile backends, and LLM/agent workflows" — but the action verbs are limited to "Design and build", so it falls just short of the comprehensive multi-action coverage of a 5.

Completeness

The "what" is clear ("Design and build reactive, type-safe, production-grade backends on Convex"), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps this dimension at 3.

Trigger Term Quality

Good natural keyword coverage ("backends", "auth", "file storage", "scheduling", "real-time multiplayer", plus the strong brand trigger "Convex"), but common synonyms a user might say ("database", "serverless", "API", "file uploads") are missing, which keeps it below comprehensive anchor 5.

Distinctiveness Conflict Risk

"on Convex" and "Convex's one-platform stack" establish a clear niche with a distinct brand trigger, but generic backend terminology ("auth", "scheduling", "mobile backends", "LLM/agent workflows") without trigger conditioning creates minor overlap risk with general backend and agent skills, fitting anchor 4 rather than the minimal-conflict anchor 5.