Conciseness

Largely lean — tables, terse key-point bullets, and command snippets with no tutoring of generic Postgres knowledge; the opening Lakebase-architecture context is platform-specific and earns its tokens. It falls short of the lean/efficient 5 anchor because pooled-vs-direct guidance recurs in three places (the connection-type table under Setup Flow, the Migrations section, and the Gotchas section), which could be consolidated. Not 3: no padded explanations of concepts Claude already knows.

Actionability

Mostly executable: concrete commands (`neon inspect db <check>`, `neon connection-string`, `neon skills -s neon-postgres-branches -y`), run-ready SQL (`EXPLAIN (ANALYZE, BUFFERS, PREFETCH, FILECACHE)`), exact env var names (`DATABASE_URL` / `DATABASE_URL_UNPOOLED`), CLI flags, MCP tool names, and real error signatures (SQLSTATE 25006, `prepared statement "s0" already exists`). Minor gaps keep it below fully-executable coverage: several sections (IP Allow Lists, Logical Replication, Autoscaling) are a 'Use this when' sentence plus a bare doc link with no inline command or example.

Workflow Clarity

The Performance Workflow (steps 1-5) has explicit validation ('Re-run the same check and workload to verify the change') and error-recovery loops (retry a failing database with an explicit `databaseName`), and the Migrations section mandates testing on a branch before production — satisfying the database-operations feedback-loop expectation. The Setup Flow (steps 1-4) is clearly sequenced with decision branches (use an existing DATABASE_URL; read .env before overwriting) but lacks a connection-verification checkpoint, which is the minor validation gap separating this from the 5 anchor.

Progressive Disclosure

The body is a well-organized overview that routes detail to four real, one-level-deep reference files, each clearly signaled and purpose-labeled in the Lakebase Search section ('For semantic search, read [Vector search](references/vector-search.md)' etc. — all four files exist in references/). Sibling-skill delegation (neon-postgres-branches, postgres-best-practices) is explicit with fetch commands, and per-topic neon.com doc links are cleanly separated from the bundle. Matches the clear-overview anchor with nothing inlined that belongs in a separate file.

Specificity

Enumerates eleven concrete capability areas ("connections, pooled vs direct, schema migrations, branching, autoscaling, scale-to-zero, instant restore, read replicas, IP allow lists, logical replication, and Lakebase Search") under the generic frame "Guides and best practices for working with". Coverage is comprehensive and specific to the domain, but capabilities are named as topic areas rather than concrete actions, so it sits between the 4 and 5 anchors — clearly above '1-2 concrete actions' (3).

Completeness

Explicitly answers both what ("Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, ...") and when ("Use when the work is an existing DATABASE_URL, SQL, schema, inspect, or search. Also use for ..."), with a concrete when-not boundary ("New backends, Auth, files, Functions, and LLM calls go to the parent `neon` skill"). This matches the anchor requiring clear what AND when with concrete trigger phrases.

Trigger Term Quality

Extensive natural trigger coverage including exact user-facing strings: "DATABASE_URL", "SQL", "schema", "inspect", "search", "@neondatabase/serverless", "@neondatabase/neon-js", "neon inspect db", "semantic search", "vector search", "full-text search", "BM25", "hybrid search". Package names, a CLI subcommand, and search synonyms make this a clear match for the comprehensive-coverage anchor.

Distinctiveness Conflict Risk

Claims a clear niche (Lakebase Postgres on Neon via a specific driver/CLI ecosystem) and actively reduces overlap risk by routing sibling topics to the parent skill ("Auth, files, Functions, and LLM calls go to the parent `neon` skill"). Distinct trigger strings like "neon inspect db" and "@neondatabase/serverless" are unlikely to fire the wrong skill — matches the minimal-conflict anchor.