PlugWiki

Neon Auth Skill for Claude Code: What It Does and How to Install It

Makes your assistant add login to an app with Neon Auth (Managed Better Auth), with users and sessions stored in your Neon database.

Installs
25K
on skills.sh
Stars
108
on GitHub
Files
3
besides SKILL.md
Updated
Oct 2026
last repo commit

SKILL.md first decides which identity route fits: Managed Better Auth for a new app, or keep a working provider. For Managed Auth it adds auth: true to neon.ts, runs neon deploy, and then implements login from a reference file.

It loads for requests like add auth, add login, passkeys, MFA or OAuth for an MCP server. It needs the Neon CLI and an AWS-region project. It bundles 3 reference files and points to the parent neon skill first.

Good for

  • Developers adding sign-up and sign-in to a new app on Neon
  • Teams moving off Supabase Auth
  • Builders who need an OAuth server for an MCP server

Install neon-auth

Claude Code

  1. 1

    Copy this prompt.

    Install the neon-auth skill in Claude Code. Run this command:
    
    npx skills add neondatabase/agent-skills --skill neon --skill neon-auth
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js, A Neon account.

Install the parent neon skill with this one: SKILL.md starts with 'Use the parent neon skill', and the commands here use the Neon CLI. The parent neon skill gives the CLI install (npm i -g neon, plus bun, pnpm or brew variants) and sign-in (neon login). The plugin route installs the neon-postgres plugin: 9 skill folders and the Neon MCP server (https://mcp.neon.tech/mcp), which asks you to sign in with Neon over OAuth on first use. The folder routes copy skills only. There is no Claude app upload route because the skill drives the Neon CLI.

Built from the package data we hold. Not yet tested by us.

What's in the skill

When it loads

Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, OAuth server for MCP or third-party OAuth clients, passkeys, MFA, trusted domains, invalid domain, and @neon/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neon/neon-js.

Sections in SKILL.md

  1. When to Use
  2. What It Does
  3. Availability
  4. Managed setup
  5. Supabase Auth
  6. Verification
  7. Plugin support
  8. Apple and Microsoft OAuth
  9. Trusted domains
  10. Functions and Data API

Key facts

Installs on skills.sh
24,964 (Nov 2, 2026)
Last repo commit
Oct 30, 2026

What it includes

  • Picks Managed Better Auth for new apps, or keeps a working provider such as Clerk.

    If a required plugin is outside Managed support, it uses self-managed Better Auth.

    Try: “Add login to my new app.”

    Read · Identity routing

  • Adds auth: true to neon.ts, then neon deploy and neon neon-auth status.

    Not available on a project with IP Allow or Private Networking.

    Runs code · Managed setup

  • Implements login in the app with the Managed Better Auth client.

    Write · references/managed-auth.md

  • Makes Neon Auth the OAuth server for an MCP server or OAuth clients.

    Write · references/oauth-server.md

  • Runs self-managed Better Auth on a Neon Function or the existing host.

    Write · references/self-managed.md

  • Recommends Managed Better Auth and follows the Neon migration guide.

    SKILL.md says the guide lists Supabase phone/SMS/WhatsApp, SAML and Web3 as unsupported.

    Write · Supabase Auth migration

  • Lists which Better Auth plugins Managed Auth supports.

    Read · Plugin support

  • Adds or updates Apple and Microsoft OAuth with your own credentials.

    Runs code · neon neon-auth oauth-provider

  • Adds, lists and deletes trusted domains.

    Delete · neon neon-auth domain

From the official docs

Permissions

Medium risk

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It writes your auth code

    The skill sets up sign-up, sign-in and sessions, and can migrate login from Supabase Auth. Review the code and test sign-in before you ship. github.com

  • Trusted domains control sign-in

    neon neon-auth domain add and delete change which origins may use auth. SKILL.md says localhost ports are pre-approved by default. github.com

  • OAuth secrets go through the CLI

    Apple and Microsoft need your own credentials. SKILL.md says a multi-line secret goes in a file passed with --oauth-client-secret-file. Keep that file out of git. github.com

Technical details
Turning on read-onlyNo read-only mode is documented for this skill.
Talks toNeon API through the CLI. Your app host and OAuth providers
Sign-in and keysUsers, sessions and auth config live in the neon_auth schema on the branch Postgres. CLI access uses your Neon sign-in or API key.
Scopes
  • Runs the Neon CLI as your Neon account

  • Writes login and session code in your app

  • Enables Managed Better Auth on a branch, with users and sessions in the neon_auth schema

  • Handles OAuth client secrets for Apple and Microsoft

Questions

What does the neon-auth skill do?

It helps your assistant add login to an app with Neon Auth, which is Managed Better Auth. Users and sessions live in your Neon database and branch with it. It also covers OAuth, trusted domains and migrating from Supabase Auth.

How do I install it?

Use the install box at the top of this page. It installs the parent neon skill with this one, because SKILL.md starts by pointing to the neon skill. You also need the Neon CLI and a Neon account.

Is it the official Neon skill?

Yes. It is in Neon's own agent-skills repo, and the repo's marketplace file calls its plugins official Neon plugins for Claude Code.

Does it work in the Claude app?

The install box has no Claude app upload route, because the skill drives the Neon CLI on your machine.

Will it replace my current login system?

No by default. SKILL.md says to keep a working Better Auth, Clerk, Supabase Auth or other identity provider unless you ask to migrate. A new app with no identity gets Managed Better Auth.

When does it use self-managed Better Auth?

When a required plugin is outside Managed support. SKILL.md then hosts Better Auth on a Neon Function or on the existing app host.

Is it safe?

It writes login code and changes who may sign in. Our advice: work on a branch, review the auth code and test sign-in and sign-out before merging.

Information

updated Nov 2, 2026

Folder
skills/neon-auth

neondatabase/agent-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6
  1. neondatabase/agent-skills README · github.com
  2. neon marketplace.json · github.com
  3. neon plugin.json · github.com
  4. neon mcp.json · github.com
  5. neon SKILL.md (parent skill) · github.com
  6. neon-auth SKILL.md · github.com

Updated Nov 2, 2026.