neon

Provision and manage Neon serverless Postgres, Auth, Functions, Object Storage, and AI Gateway backends.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @neon/config, @neon/env, @neon/sdk, @neon/functions, and includes references (resource) components.

What problem does it solve? Setting up a cloud backend requires stitching together a database, authentication, file storage, serverless compute, and LLM access across multiple vendors. This Skill guides an AI agent through provisioning and operating Neon's complete set of backend primitives around Lakebase Postgres from a single platform, using the CLI, MCP server, or a no-signup Claimable path. ## Core Features & Use Cases - Backend Primitive Selection: Maps app requirements (login, files, APIs, LLM calls, SQL) to the right Neon primitive — Lakebase Postgres, Managed Better Auth, Object Storage, Functions, or AI Gateway — while preserving existing providers like Clerk, Supabase Auth, or a supplied DATABASE_URL. - Branch-First Development: Drives a copy-on-write branch workflow with neon checkout, env pull, and schema diff so every feature gets an isolated database clone. - Infrastructure as Code: Declares services in a type-safe neon.ts config file and reconciles them with neon status, plan, and deploy, including Function Triggers on cron or storage events. - Use Case: A developer asks an agent to add login and file uploads to a new app. The Skill checks credentials, runs neon init or the Claimable flow, declares auth and buckets in neon.ts, deploys, and verifies the sign-in and upload flow end to end. ## Quick Start Ask the agent to set up a Neon backend with Postgres and authentication for your app, and it will check the CLI, link or claim a project, and provision the services.

Frequently Asked Questions about neon

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

FAQPage Schema
How do I set up a Neon Postgres database for my app?▼

Install the Neon CLI with npm i -g neon, then run neon init to link or create a project and pull the DATABASE_URL into your env file. If you have no account, the Claimable Neon path provisions a temporary project without signup.

How do I add authentication to a Neon project?▼

Use the neon-auth skill, which implements Managed Better Auth with users and sessions stored in Postgres. Declare auth: true in neon.ts and run neon deploy, or keep an existing provider like Clerk or Better Auth if one already works.

Should I use the Neon Data API or query Postgres directly?▼

Query Postgres directly from Neon Functions or existing app route handlers for new apps. The Data API is a PostgREST compatibility path only for apps already using PostgREST or a Supabase database client, or migrations that depend on it.

Can I use Neon Functions and Object Storage in any region?▼

No. Object Storage, Functions, and AI Gateway are available only in aws-us-east-2, aws-us-east-1, aws-eu-central-1, and aws-ap-southeast-1. Projects in other regions need a new project in a supported region.

What is Claimable Neon and when should I use it?▼

Claimable Neon provisions a temporary project with Postgres and optional Auth before a human creates an account, using neon claim create. Unclaimed projects expire after 72 hours, and Functions, Object Storage, and AI Gateway stay denied until a human claims the project.

Why does neon.ts show a type error when I enable the Data API?▼

The Data API verifies requests with Neon Auth by default, so enabling dataApi alone is a type error. Fix it by adding auth: true, or set authProvider to external with a jwksUrl pointing at your third-party identity provider.