Conciseness

The body is product-specific (no padding about concepts Claude already knows), but guidance is noticeably repeated: the Data API caution appears at least four times ("Use it only when the app already uses PostgREST...", "Do not recommend this for new apps", "There is no neon-data-api skill", "Use data-api only for PostgREST / Supabase database-client compatibility"), the "link and checkout run this for you by default" env-pull note repeats three times, and the supported-region list is duplicated verbatim. Mostly efficient but could be tightened — anchor 3, not 2 since nothing explains generic known concepts.

Actionability

Fully executable, copy-paste-ready guidance throughout: exact CLI commands with flags ("neon init --agent cursor --org-id <org-id> --project-id <project-id> -y", "neon mcp --oauth --project --agent <agent> -y"), complete defineConfig TypeScript examples, install commands, and concrete flag semantics ("-y skips prompts but does not supply project selection or credentials"). Specific examples cover the common setup, deploy, branch, and logging cases.

Workflow Clarity

Setup and convert-app flows are clearly sequenced with most checkpoints present: "Verify the app flow (sign-in, upload, API call), not only that env vars landed", the "neon config plan" dry-run before apply, env-pull failing fast and pointing at "neon deploy --env <file>", and auth failures routed to "stop and ask the user to sign in". Not 5 because the combined-init and manual-steps paths interleave without a single top-level sequence, and a few checkpoints are implicit (no explicit post-deploy verification step).

Progressive Disclosure

Six real one-level-deep reference files exist in the bundle and are clearly signaled in the body ("[references/logs-loki.md]", "[references/claimable-neon.md]"), with deep material (Claimable flow, trigger parsers, LogQL, SDK, parseEnv) correctly pushed out of the overview. Not 5 because the ~130-line neon.ts / type-safe-config section is detailed inline material that belongs in a reference (it points only to a docs URL, no bundle file), and body reference links point to web URLs rather than the local bundle files.

Specificity

Enumerates the full capability surface ("Auth, Object Storage, Functions, and the AI Gateway") and multiple concrete actions ("choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow"). Coverage is comprehensive with no minor gaps, matching the anchor-5 pattern rather than anchor 4.

Completeness

Explicitly answers both what ("Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres") and when ("Use when building an app or backend on Neon, or when 'Neon' or 'Lakebase Postgres' is mentioned", plus an "Also use for" list). Both are concrete and explicit, matching the anchor-5 example structure.

Trigger Term Quality

Comprehensive natural trigger terms including synonyms and product-specific phrases: "login, files, APIs, LLM calls... S3, buckets, cron, AI gateway, logs, Loki, Grafana, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database" plus "DATABASE_URL, SQL, schema, inspect, or search". Essentially no natural term a user would say is missing.

Distinctiveness Conflict Risk

Child-skill delegation ("Child skill neon-postgres wins for an existing DATABASE_URL...") actively disambiguates within the Neon family, but the broad tail terms ("postgres, database, backend, logs, observability") overlap with generic Postgres and observability skills. Mostly distinct with minor overlap risk — anchor 4, not 5.