neon-postgres

Guides connections, migrations, branching, diagnostics, and search on Neon Postgres databases.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/akira777777/vladfsBET --skill neon-postgres-akira777777
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neon-postgres
Source: https://github.com/akira777777/vladfsBET/tree/main/.grok/skills/neon-postgres
Command: npx skills add https://github.com/akira777777/vladfsBET --skill neon-postgres-akira777777

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with Neon Postgres involves platform-specific decisions—pooled versus direct connections, branch-based migration testing, scale-to-zero behavior, and Neon-specific diagnostics—that generic Postgres knowledge does not cover. This Skill provides the operational guidance to configure, migrate, troubleshoot, and extend a Neon database correctly. ## Core Features & Use Cases - Connection & Schema Setup: Choose between pooled and direct connection strings, pick the right driver for serverless or edge runtimes, and manage migrations as code. - Branching, Restore & Scaling: Use copy-on-write branches for isolated environments, instant point-in-time restore, autoscaling, read replicas, and scale-to-zero cost optimization. - Diagnostics & Search: Run predefined read-only inspection checks (table sizes, unused indexes, locks, cache hit rates) and implement semantic, full-text BM25, and hybrid search with Lakebase Search extensions. - Use Case: A developer deploying a serverless app on Vercel needs to run a Prisma migration safely. The Skill directs them to use the direct (non-pooled) connection string, test the migration on a branch of production first, then verify with neon inspect db checks. ## Quick Start Ask the AI to help you connect your application to your Neon database and set up the schema using the existing DATABASE_URL.

Frequently Asked Questions about neon-postgres

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

FAQPage Schema
How do I connect to a Neon Postgres database?▼

Get the connection string via the Neon CLI, `neon env pull`, or the MCP server and store it as DATABASE_URL in your .env file. Use the pooled connection for application traffic and the direct connection for migrations and admin tasks.

When should I use pooled vs direct Neon connections?▼

Use the pooled (-pooler) connection for web applications and serverless functions with bursty concurrency. Use the direct connection for schema migrations, pg_dump/pg_restore, logical replication, LISTEN/NOTIFY, and anything relying on session state like SET.

Why does my Prisma migration fail on Neon?▼

Migrations fail over the pooled connection because PgBouncer transaction mode does not support session-level operations, causing errors like prepared statement conflicts. Point Prisma's directUrl at the direct (non-pooled) connection string instead.

How do I test a database migration safely on Neon?▼

Create an instant copy-on-write branch of production and run the migration there against production-like data first. Use a direct connection string for the migration, then apply it to production once verified.

Does Neon support vector and full-text search?▼

Yes, Lakebase Search on Postgres 16+ provides the lakebase_vector extension for semantic ANN search and lakebase_text for BM25 full-text ranking. Hybrid search combines both retrievers using fusion strategies like Reciprocal Rank Fusion.

How do I diagnose slow queries on Neon?▼

Run predefined read-only checks with `neon inspect db` or the MCP inspect_database tool, such as outliers, long-running-queries, and lfc-hit-rate. For per-query cache behavior, use EXPLAIN (ANALYZE, BUFFERS, PREFETCH, FILECACHE) on safe read-only statements.