neon

Provision and configure Neon cloud backend primitives including Lakebase Postgres, Auth, Functions, and Object Storage.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/Abhi-0930/online--lms --skill neon-abhi-0930
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neon
Source: https://github.com/Abhi-0930/online--lms/tree/main/backend/.agents/skills/neon
Command: npx skills add https://github.com/Abhi-0930/online--lms --skill neon-abhi-0930

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 choosing and wiring together a database, authentication, file storage, serverless compute, and LLM access. This Skill guides an AI agent through provisioning and configuring Neon's backend primitives around Lakebase Postgres, using the CLI, MCP server, and branch-first development workflow. ## Core Features & Use Cases - Backend Primitive Selection: Maps app capabilities (login, files, APIs, LLM calls, SQL) to the right Neon primitive — Auth, Object Storage, Functions, AI Gateway, or the Data API — while preserving existing providers like Clerk or S3. - CLI and MCP Setup: Walks through installing the Neon CLI, MCP server, and agent skills, linking projects, and pulling branch environment variables. - Infrastructure as Code: Declares services in a type-safe neon.ts config and reconciles them with neon status, neon config plan, and neon deploy. - Use Case: When building a new app, ask the agent to set up a Neon project with Postgres and Auth; it provisions a claimable or linked project, writes neon.ts, deploys the services, and pulls DATABASE_URL into your local env. ## Quick Start Ask the agent to set up a Neon project for your app with Postgres and authentication using the Neon CLI.

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 a new app?▼

Install the Neon CLI with npm i -g neon, then run neon init to link or create a project and pull environment variables. Without an account, use the Claimable Neon path via neon claim create to provision a temporary project with Postgres.

What Neon primitive should I use for login, file uploads, or LLM calls?▼

Use managed Auth for login and sessions, Object Storage for files and uploads, Functions for HTTP APIs and long-running compute, and the AI Gateway for LLM calls. SQL and schema work belongs to the neon-postgres skill, and the Data API is only for PostgREST or Supabase client compatibility.

Does Neon Auth work with IP Allow or Private Networking enabled?▼

No, managed Better Auth cannot be enabled on projects using IP Allow or Private Networking. Leave those protections in place and choose another auth provider for that project instead.

How do Neon branches work in a development workflow?▼

Create a Neon branch whenever you would create a git branch using neon checkout <name> --create, which also pulls that branch's env vars. Use neon diff to view schema changes against the parent branch before committing.

When should I use the Neon Data API instead of Functions?▼

Use the Data API only when an app already relies on a PostgREST or Supabase database client, or is migrating one. New apps should query Postgres from Neon Functions or existing route handlers rather than defaulting to the Data API.