Neon

This is your entry point for working with Neon's full backend platform, which has grown well beyond just Postgres. It covers serverless Postgres, Auth, Object Storage, Compute Functions, and the AI Gateway. The skill's main job is routing you to the right specialized skill based on what you're trying to build, whether that's managing database branches, storing files, deploying long-running functions, or calling LLMs. It also walks through the branch-first workflow and explains how Neon composes with your existing app platform like Vercel rather than replacing it. Most useful when you're first setting up Neon or adding a new service to an existing project.

skills.sh installs: 260.2K
GitHub stars: 113
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add neondatabase/agent-skills --skill neon --agent claude-code

Installs into .claude/skills of the current project.

Files

Neon

Neon is a complete set of cloud backend primitives around Lakebase Postgres, from Databricks — Lakebase Postgres, Auth (managed Better Auth), long-running Functions, Object Storage, an AI Gateway, and Realtime live queries, all instant, branchable, and serverless.

Lakebase Postgres is the database itself. It is one product, reached two ways: through Neon, with a free plan and the full set of backend primitives above, or through Databricks, alongside the rest of the Databricks suite. Same infrastructure, same features, same engineering team. Call the database Lakebase Postgres, and use "Neon" for the brand and for this access path — not as a name for the database.

A Neon branch is an isolated, copy-on-write clone of your data, taken from its current state or from a past state within your project's retained history window. You can freely modify or delete it. It shares data with its parent until writes cause it to diverge, and those writes are stored independently as deltas.

SKILL.md on GitHub