Conciseness

The body is lean: no explanations of concepts Claude already knows, tight workflow steps, and compact code examples. A few rationale clauses could be trimmed, e.g., "This keeps Git, development, and production reproducible; the tradeoff is that experiments require a new migration version" and the two-sentence intro, which fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place anchor at 5.

Actionability

Mostly executable guidance: a complete CREATE POLICY example, an idiomatic batched-read TypeScript snippet with error handling ("if (error) throw error"), and a concrete API call (`queryEnv(action="info", envId=...)`). Minor gaps keep it below 5: keyset pagination is named ("an RPC that implements keyset pagination") without an example, and `.limit()` / `.range()` bounding is described but not shown.

Workflow Clarity

The four-step workflow has explicit validation gates ("**Complete when:**" after every step), error/escalation paths ("marked as an assumption for the user", "raised to the user as an unresolved launch blocker"), and a closing "Minimum self-check" checklist. This matches the anchor for clear sequence with explicit validation steps and checklists; validation is present, so the database-operations cap does not apply. Not score 4 because checkpoints are explicit and comprehensive rather than minor-gapped.

Progressive Disclosure

The Routing table maps each work branch to one of four real, one-level-deep reference files (access-patterns.md, indexes-and-explain.md, schema-and-rls.md, capacity-and-connections.md), all verified present in the bundle and matching their routing descriptions, with the explicit instruction "Load only the references required by the current branch." Clear overview with well-signaled references and easy navigation — the top anchor.

Specificity

Names the domain ("CloudBase PostgreSQL access-pattern and slow-query quality guidance") and lists multiple concrete actions: "designing how tables are read and written", "eliminating per-row database calls", "adding indexes for filters or joins", "reviewing high-traffic data access", and "explaining a slow SQL query". This matches the anchor for multiple specific concrete actions with comprehensive coverage; there is no vague filler to push it down.

Completeness

Explicitly answers 'what' ("CloudBase PostgreSQL access-pattern and slow-query quality guidance") and 'when' with concrete trigger phrases ("Use when designing how tables are read and written, eliminating per-row database calls, adding indexes..."). It also adds an explicit exclusion clause ("Not for first-time PG SDK setup, login UI, or NoSQL collections"), matching the top anchor; not score 4 because the 'when' guidance is already fully explicit with concrete triggers.

Trigger Term Quality

Good natural keyword coverage: "slow SQL query", "adding indexes", "per-row database calls", "high-traffic data access" are phrases users would plausibly say. A few natural terms are missing, such as "N+1", "query performance/optimization", or "database readiness", so it fits the 'good coverage, a few natural terms missing' anchor rather than the comprehensive-synonym anchor at 5.

Distinctiveness Conflict Risk

Clear niche (CloudBase PG access patterns and slow queries) with distinct triggers and explicit de-scoping of adjacent concerns ("Not for first-time PG SDK setup, login UI, or NoSQL collections"). Minimal conflict risk with other skills; not score 4 because no meaningful overlap risk remains unaddressed.