Conciseness

Lean and efficient throughout: dense limit tables and rule statements like 'Do not use .filter()... neither pushes the predicate to storage' and 'Skip no-op writes: compare before ctx.db.patch()'. It assumes Claude's competence, explains nothing generic, and every token earns its place — matches the 5 anchor; not 4 because there are no sections that could be trimmed.

Actionability

Mostly executable guidance: concrete commands ('npx convex dev', 'npx convex deploy', 'npx convex import', 'npx convex insights', 'npx convex codegen') and exact API identifiers (v.null(), .withIndex(), internalMutation). However, the key batching pattern ('paginate({ cursor, numItems }) ... ctx.scheduler.runAfter') is sketched inline in prose rather than as a complete, copy-paste-ready example — a minor gap fitting the 4 anchor; not 5 because the most important pattern is not fully executable as written, and not 3 because the guidance is concrete, not pseudocode.

Workflow Clarity

The Deploy Loop gives a clear sequence (dev → verify → deploy) with a checkpoint table and an explicit rollback path, and the batching rule addresses batch-operation safety. Minor gaps remain: 'verify' and checkpoints like 'checklist completed' / 'Smoke check passes' are not fully specified, and the destructive batch/migration flows rely on implicit validation — fits the 4 anchor; not 5 because checkpoints are named but not all are actionable validation steps, and not 3 because a real sequence with explicit checkpoints is present.

Progressive Disclosure

Compact (~75 lines), well-organized sections, and external material is clearly signaled one level deep (the project-specific '.opencastle/stack/database-config.md' and https://docs.convex.dev/). No bundle files exist to split further, and the body is appropriately sized for the main file — matches the 5 anchor under the simple-skill guidance.

Specificity

Lists multiple specific concrete actions — 'schema design, real-time queries, mutations, actions, authentication, migrations, performance optimization, and component creation' — with comprehensive coverage of the domain, matching the top anchor; not 4 because there are no notable gaps in the action list.

Completeness

Both parts are explicit: a clear 'what' (first sentence enumerating capabilities) and a concrete 'when' ('Use when designing Convex schemas, writing queries/mutations, ... or building Convex components'), matching the 5 anchor exactly; not 4 because the 'when' clause is explicit and specific rather than improvable.

Trigger Term Quality

Good natural keyword coverage ('Convex schemas', 'writing queries/mutations', 'managing the Convex backend', 'setting up auth', 'migrating data', 'optimizing performance'), but a few natural phrasings users might say (e.g., 'real-time data', 'Convex functions', config file work) are missing — the 4 anchor 'good keyword coverage; a few natural terms missing' is the best fit.

Distinctiveness Conflict Risk

'Convex' names a clear niche with distinct triggers, so it is unlikely to fire for other database/backend skills — minimal conflict risk per the 5 anchor.