Conciseness

The body is lean: tight tables for window functions, joins, index types, and anti-patterns with minimal prose and copy-paste SQL, assuming Claude already knows SQL; the only trimming target is the redundant opening line "Quick reference for common SQL patterns." which restates the description, keeping it just below the anchor-5 "every token earns its place" bar.

Actionability

Multiple complete, executable SQL blocks (single CTE, chained CTE, a window-function query using LAG/SUM OVER, and both OFFSET and keyset pagination) are copy-paste ready and cover the common cases, matching the anchor-5 "fully executable; specific examples cover the common cases" example.

Workflow Clarity

This is a reference card with no multi-step process, so there is no sequenced workflow or validation checkpoint to evaluate; it is well organized into sections but, being a multi-topic lookup rather than a single-task skill, it does not meet the simple-skill exception for a 5 and lands at the anchor-3 middle where sequence/checkpoints are absent (appropriately, since the patterns are read-only and non-destructive).

Progressive Disclosure

The body is well sectioned and signals one-level-deep references in "Additional Resources" ("./references/window-functions.md", "./references/indexing-strategies.md"), but those referenced files do not exist in the bundle (no references/ directory), so the signaled navigation is dead — a real navigation failure that pulls it below anchor 4 despite good in-file structure.

Specificity

Quotes "Quick reference for common SQL patterns, CTEs, window functions, and indexing strategies" name the SQL domain plus several concrete topics, but the only action is the generic verb "reference for", lacking multiple distinct concrete actions like the anchor-4 "extracts/fills/converts" example; it sits above anchor 2 (which would name only the domain) yet below anchor 4 (which requires several specific actions).

Completeness

It states a clear "what" ("Quick reference for common SQL patterns, CTEs, window functions, and indexing strategies") and an explicit "when" via the "Triggers on:" clause with concrete trigger phrases, directly matching the anchor-5 pattern of answering both what and when with concrete triggers; the "Use when" cap at 3 does not apply because explicit trigger guidance is present.

Trigger Term Quality

The explicit "Triggers on: sql patterns, cte example, window functions, sql join, index strategy, pagination sql" gives good natural keyword coverage a user would actually say, but it stops short of anchor-5 comprehensive coverage because it omits synonyms and file extensions (e.g. no .sql, no "recursive CTE", no "query optimization").

Distinctiveness Conflict Risk

The SQL-patterns niche with distinct triggers (CTEs, window functions, joins, indexing, pagination) is clearly distinguishable from non-SQL skills, but terms like "sql join" and "window functions" could overlap with a broader general database/SQL skill, so it is "mostly distinct; minor overlap risk" rather than the minimal-conflict anchor 5.