neon-postgres
Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching, autoscaling, scale-to-zero, instant restore, read replicas, IP allow lists, logical replication, and Lakebase Search. Use when the work is an existing DATABASE_URL, SQL, schema, inspect, or search. New backends, Auth, files, Functions, and LLM calls go to the parent `neon` skill. Live queries, reactive UIs, and realtime data go to `neon-realtime`. Also use for "@neondatabase/serverless", "@neon/neon-js", "neon inspect db", "semantic search", "vector search", "full-text search", "BM25", or "hybrid search".
Install
With your agent
Install OMGSkills skill "neondatabase/agent-skills:neon-postgres" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/neondatabase/agent-skills /tmp/agent-skills && ln -s /tmp/agent-skills/skills/neon-postgres ~/.claude/skills/neon-postgresFrom README
Lakebase Postgres 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. Flow Select the organization and project If a DATABASEURL 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. Otherwise use the CLI (default) or MCP server to list organizations and projects. Let the user select an existing project or create a new one.
More from this repo
neon-postgres-egress-optimizer
Diagnose and fix excessive Postgres egress (network data transfer) in a codebase.
neon
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions,...
neon-ai-gateway
One API and one credential for frontier and open-source LLMs and embedding models, built into your Neon branch and...