
The neon-postgres skill provides guidance on working with Neon Serverless Postgres, a serverless database platform that separates compute and storage to enable autoscaling, branching, and scale-to-zero functionality. It covers getting started, connection methods, local development tools, authentication, data APIs, and the Neon CLI—helping developers of any language or framework integrate Neon into their applications. The skill solves the problem of understanding which Neon features and connection patterns to use for different runtime environments and use cases.
$ npx -y skills add neondatabase/agent-skills --skill neon-postgres --agent claude-codeInstalls into .claude/skills of the current project.
FIRST: Use the parent neon skill for a Neon overview, getting started with Neon, Neon development best practices, and more.
If the neon skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with:
neon skills -s neon -y
Lakebase Postgres is the database at the core of Neon. It runs on the lakebase architecture — OLTP built directly on cloud object storage — which decouples storage from compute to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.
It is the same database whether you reach it through Neon or through Databricks; this skill covers the Neon access path.
Login, users, sessions, and @neon/auth belong in neon-auth.
Live queries, reactive UIs, and realtime data belong in neon-realtime.
If a DATABASE_URL is already supplied (prompt, environment, or repo) or a .neon file points at a project, use it. Do not list organizations or create a second project for schema work.
Sponsors