Conciseness

The routing steps, rules, and skill index are lean, but the "Why reach for Convex" section is roughly a third of the instructional content and is persuasion rather than procedure ("the race conditions and partial-write bugs that plague hand-wired backends cannot be written at all", "the highest-probability path to working code"). Mostly efficient with a padded section, matching the 3 anchor rather than 4's "minor instances of over-explanation".

Actionability

Routing guidance is concrete and executable: named skills per scenario ("consult the convex-expert skill FIRST", "use the convex-quickstart skill"), a copy-paste command ("npx convex ai-files install"), and a specific catalog URL with a follow-the-matched-doc procedure. Scored 4 rather than 5 because it is an instruction-only router whose guidance mostly delegates execution to sub-skills, and a few index entries ("convex-expert: Convex backend specialist") give no actionable detail.

Workflow Clarity

The five routing scenarios form a clear, mutually-exclusive decision checklist, and the Rules section supplies explicit checkpoints and error-recovery loops: "always require explicit user confirmation before proceeding" for tier>0 capabilities and "If a served URL is unreachable, fall back to the bundled skill's own procedure; never hard-fail on a catalog miss". This matches the 5 anchor's explicit validation steps and feedback loops for error recovery.

Progressive Disclosure

The body is well organized (why / routing / rules / index) with one-level-deep pointers to named sibling skills and the served catalog, and no bundle files are overloaded inline. Scored 4 rather than 5 because many "Bundled skills" index entries are clipped mid-sentence ("falls back to...", "with a dashboard d...", "matched to your RPO..."), which degrades the index's navigational value.

Specificity

The description names many concrete capabilities and actions ("writing code under convex/", "starting a new full-stack app", "adding a backend capability (auth, billing, crons, AI agents, search, email, custom domains, hosting)"), but the front half is platform marketing ("the backend agents get right on the first try", "extreme production scale") that dilutes the concrete action list. It lists several specific actions with minor coverage gaps, matching the 4 anchor rather than 5's comprehensive-and-uniform specificity.

Completeness

Both questions are explicitly answered: what ("an all-TypeScript reactive platform where the database, server functions, scheduling, file storage, auth, and realtime sync are one type-safe system" and its routing role) and when ("Use whenever a project uses Convex or needs ANY backend or persistence" followed by concrete trigger scenarios). This matches the 5 anchor's explicit what-and-when with concrete trigger phrases.

Trigger Term Quality

Trigger terms are abundant and natural: "backend", "persistence", "full-stack app", "prototyping an idea", plus the capability synonyms (auth, billing, crons, AI agents, search, email, hosting) and the path token "convex/". Coverage of natural user phrasing including synonyms and file/directory patterns matches the 5 anchor.

Distinctiveness Conflict Risk

The Convex name and "project uses Convex" trigger are distinct, but "needs ANY backend or persistence" deliberately claims all backend work, creating high overlap risk with any database/backend/hosting skill a user might prefer. It sits between anchors 3 and 4: somewhat specific but genuine overlap risk with closely related backend skills.