neon-postgres

Configures and manages Neon Serverless Postgres connections, branching, autoscaling, and replication.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/dhanushreddy291/durable-workflow-on-neon-functions --skill neon-postgres-dhanushreddy291
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neon-postgres
Source: https://github.com/dhanushreddy291/durable-workflow-on-neon-functions/tree/main/.agents/skills/neon-postgres
Command: npx skills add https://github.com/dhanushreddy291/durable-workflow-on-neon-functions --skill neon-postgres-dhanushreddy291

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up and operating a serverless Postgres database involves many decisions—choosing pooled versus direct connections, picking the right driver for each runtime, managing branches, and configuring autoscaling—and mistakes lead to connection failures, wasted compute costs, or broken migrations. This Skill provides structured guidance for every stage of working with Neon Serverless Postgres. ## Core Features & Use Cases - Connection Setup: Guides project selection, connection string retrieval via CLI or MCP, and choosing between pooled and direct connections based on workload type. - Driver & ORM Recommendations: Recommends the correct driver per platform (Vercel, Cloudflare, Neon Functions, serverless/edge) and pairs Neon with Drizzle for schema and migration management. - Platform Features: Covers branching, autoscaling, scale-to-zero, instant restore, read replicas, connection pooling, IP allow lists, and logical replication. - Use Case: A developer deploying a serverless API needs a Postgres database. The Skill walks them through creating a Neon project, storing DATABASE_URL in .env, selecting the pooled connection with the @neondatabase/serverless driver, and setting up Drizzle migrations. ## Quick Start Ask the assistant to help you connect your application to a Neon Postgres database and choose the right driver for your deployment platform.

Frequently Asked Questions about neon-postgres

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect my application to Neon Postgres?▼

Get the connection string using the Neon CLI, neon env pull, or the MCP server, then store it as DATABASE_URL in your .env file. Choose a driver based on your runtime, such as @neondatabase/serverless for edge environments or node-postgres for long-running functions.

When should I use pooled vs direct connections in Neon?▼

Use pooled connections (the -pooler endpoint) for web applications and serverless functions with bursty concurrency. Use direct connections for schema migrations, pg_dump/pg_restore, logical replication, LISTEN/NOTIFY, and admin tasks needing session state.

Which Postgres driver should I use for serverless or edge runtimes?▼

Use the @neondatabase/serverless driver for serverless and edge environments, with HTTP transport for one-shot queries and WebSocket for transactions. On Vercel use node-postgres with Fluid compute, and on Cloudflare use node-postgres with Hyperdrive.

Does Neon Postgres support database branching?▼

Yes, Neon branches are instant copy-on-write clones with no full data copy, and each branch gets its own compute endpoint. You can create, inspect, and compare branches using the Neon CLI or MCP server for preview deployments and migration testing.

Why does my first Neon query take longer after idle periods?▼

Neon computes suspend automatically after about 5 minutes of inactivity to save costs, causing a cold-start penalty of a few hundred milliseconds on the first query after resume. Storage stays active while compute is suspended, and the timeout is configurable.

Can Neon Postgres handle read-heavy workloads?▼

Yes, Neon read replicas provide dedicated read-only compute endpoints sharing the same storage as the primary. They are suited for analytics, reporting, and read-heavy APIs, and scale independently from the primary compute.