What does the Neon Serverless Postgres skill do?

It provides documentation-grounded guidance for working with Neon Serverless Postgres by fetching and referencing live Neon documentation rather than relying on memory. It covers setup, connection methods, drivers, ORMs, authentication, and the Platform API/CLI.

How does this skill access Neon documentation?

It fetches the index of all Neon docs via `curl https://neon.com/llms.txt` and retrieves specific pages as markdown using authenticated-header requests, explicitly avoiding guessing at documentation URLs.

What are the four main resource groups this skill organizes?

Core Guides (architecture, features, getting started, connection methods, developer tools), Database Drivers and ORMs (serverless driver, Drizzle ORM), Auth and Data API SDKs (authentication and PostgREST-style data API), and Platform API and CLI (REST API, CLI, TypeScript and Python SDKs).

When should I use this skill versus a general Postgres resource?

Use it specifically for Neon Serverless Postgres tasks like setup, branching, autoscaling, authentication, or APIs. For non-Neon Postgres providers or general database questions, it does not apply since its value is routing to Neon-specific documentation.

Who is this skill designed for?

Developers setting up or integrating with Neon Serverless Postgres, including teams migrating existing Postgres workloads to Neon's branching and scale-to-zero features, and teams automating Neon project management via CLI or SDKs.

Skill

Integrate with Neon Serverless Postgres

Name: Integrate with Neon Serverless Postgres
Availability: OnlineOnly
Author: Antigravity

Navigate Neon Serverless Postgres setup, connections, drivers, authentication, and platform management with documentation-first guidance.

Get skill

Works with neonpostgres

Antigravity

Own this? Claim it

Spark score

out of 100

Updated 22 days ago

Source checked Oct 17, 2026

Version 19.8.0

Add to Favorites

Why it matters

Leverage Neon Serverless Postgres for scalable and efficient database operations. This skill helps you set up, connect to, and utilize Neon's advanced features like autoscaling and branching within your applications.

Outcomes

What it gets done

Configure Neon database connections and authentication.

Implement Neon's serverless drivers and ORM integrations.

Utilize Neon features such as branching and autoscaling.

Manage Neon resources using the Platform API or CLI.

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-using-neon | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

A documentation-oriented skill for Neon Serverless Postgres. It maps database setup, connection choices, drivers, authentication, and resource management to the relevant upstream guidance. Use it when planning or configuring Neon workflows. Supporting reference files are external prerequisites, so steps that depend on them require obtaining and checking those files first.

What it does

Using Neon organizes guidance for Neon Serverless Postgres around the database task at hand. Neon is a Postgres-compatible platform that separates compute and storage and supports autoscaling, branching, instant restore, and scale-to-zero. The skill helps locate the relevant material for database setup, connection choices, authentication, APIs, and platform practices.

Its central rule is to consult Neon documentation before making Neon-related claims. Rather than guess a documentation path, use the documentation index to locate the appropriate page or follow the resource links. The inline guidance includes a command for retrieving that index:

curl https://neon.com/llms.txt

Core resource areas cover Neon's architecture and concepts, documentation lookup, platform features, getting started, connection methods, and developer tools. The setup area addresses projects, connection strings, dependencies, and schema. Connection guidance helps choose drivers according to the platform and runtime. The developer-tool references cover the VSCode extension, MCP server, and Neon CLI.

When to use - and when NOT to

Use the skill for questions about Neon or work involving Neon databases, connection methods, branching, autoscaling, authentication, and APIs. Its documented scope applies to Postgres-compatible languages, frameworks, and ORMs. Tasks outside that scope need different guidance.

The catalog copy includes the inline instructions but does not bundle the supporting reference files. Obtain required material from the declared upstream installation or a user-provided installation, resolve paths relative to it, and inspect the contents. Check applicable licensing and execution prerequisites. A dependent procedure cannot be claimed or run until its required reference exists; do not invent a replacement script or substitute an unrelated same-named file. Independently documented steps can proceed within authorized scope, while unavailable dependent steps must be reported.

Inputs and outputs

Start with the user's database goal, runtime, connection requirements, and available source installation. The resource map directs the work to the appropriate guidance rather than providing every procedure inline. Clarify missing inputs, permissions, boundaries, and success criteria. Outcomes still require environment-specific validation, testing, or expert review.

Integrations

The driver references cover @neondatabase/serverless for HTTP/WebSocket queries in serverless and edge functions, plus Drizzle ORM integration. Authentication guidance distinguishes @neondatabase/auth for authentication from @neondatabase/neon-js for authentication and a PostgREST-style Data API.

For programmatic platform management, the map points to the REST Platform API, terminal and CI/CD workflows through Neon CLI, the @neondatabase/api-client TypeScript SDK, and the neon-api Python package. These are separate reference areas selected according to the requested workflow and the material actually available.

FAQ

Common questions

Discussion