neon-postgres
Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/andrelandgraf/neon-postgresWhat This Skill Does
The neon-postgres skill serves as your definitive AI companion for building on top of the Neon Serverless Postgres platform. It provides the AI agent with deep, contextual knowledge about Neon's unique architecture—specifically its separation of storage and compute, which enables features like instant branching, autoscaling, and zero-latency scale-to-zero capabilities. Beyond theoretical understanding, the skill enables the AI to provide concrete implementation guidance, helping you select the appropriate driver (like the @neondatabase/serverless package for edge environments) and configuring authentication workflows using the @neondatabase/auth module. It bridges the gap between raw documentation and actionable code generation, ensuring that your database interactions follow Neon's best practices.
Installation
To integrate this skill into your OpenClaw environment, use the following terminal command:
clawhub install openclaw/skills/skills/andrelandgraf/neon-postgres
Once installed, ensure your environment has the necessary API keys if you intend to use the Neon Platform API or management CLI functionalities.
Use Cases
- Cloud-Native Architecture: Designing database schemas that leverage Neon's branching capabilities for CI/CD pipelines or feature-gated development environments.
- Edge Computing Optimization: Implementing database connections that avoid TCP handshake overhead by utilizing Neon’s HTTP-based serverless drivers in Vercel, Cloudflare Workers, or similar serverless runtimes.
- Local-to-Production Sync: Using the
neonctltool and provided developer tools to mirror production database states locally for reliable testing. - Database Migration: Scripting automated migrations using Neon's CLI and Platform API for production deployments.
Example Prompts
- "I'm building a Next.js app on Vercel. Which driver should I use to connect to my Neon database to ensure minimal latency, and can you provide a code example?"
- "Explain how I can use Neon branching to test a database schema migration without affecting my production data."
- "Help me write a script using the Neon Platform API that lists all active endpoints for my project and returns their connection strings."
Tips & Limitations
Always verify specific API syntax by allowing the agent to fetch the latest documentation via .md URL requests, as Neon's SDKs evolve rapidly. Treat the documentation index (https://neon.com/docs/llms.txt) as your primary source of truth. When troubleshooting, prioritize Neon-specific connection methods over generic Postgres libraries to prevent connection pooling exhaustion and runtime errors in serverless environments.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-andrelandgraf-neon-postgres": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: external-api
Related Skills
claimable-postgres
Provision instant temporary Postgres databases via Claimable Postgres by Neon (neon.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASE_URL for prototyping/tests, or "just give me a DB now". Triggers include: "quick postgres", "temporary postgres", "no signup database", "no credit card database", "instant DATABASE_URL", "npx neon-new", "neon.new", "neon.new API", "claimable postgres API".
neon-postgres-egress-optimizer
Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, "why is my Neon bill so high", "database costs jumped", SELECT * optimization, query overfetching, reduce Neon costs, optimize database usage, or wants to reduce data sent from their database to their application. Also use when reviewing query patterns for cost efficiency, even if the user doesn't explicitly mention egress or data transfer.