{"slug": "neon-skills-landed-in-the-vercel-cli", "title": "Neon skills landed in the Vercel CLI", "summary": "Vercel's CLI now installs provider agent skills when adding a Marketplace integration, enabling a single command to provision a Neon database and equip coding agents with usage instructions. The `vercel integration add neon` command creates a Neon account if needed, bills through Vercel, and supports preview branches that give each Vercel Preview Deployment an isolated Neon branch. This streamlines database provisioning and agent-driven development workflows.", "body_md": "[Vercel just gave their CLI a new trick](https://vercel.com/changelog/vercel-marketplace-agent-skills): when you install a Marketplace integration from the terminal, it also installs that provider's agent skills. A single command now provisions a Neon database on your Vercel project and hands your coding agent the instructions it needs to actually use it:\n\n## Provision Neon from the Vercel CLI\n\nIf you deploy to Vercel, you've probably used the CLI mostly for `vercel deploy`\n\nor `vercel env pull`\n\n. The part that matters here is a different subcommand, [ vercel integration](https://vercel.com/changelog/vercel-cli-for-marketplace-integrations-optimized-for-agents), which manages\n\n[Marketplace integrations](https://vercel.com/marketplace)from the terminal. You can use this command to provision a resource from a Marketplace integration (e.g. a Neon backend), and if that integration isn't installed on your team yet, it installs it first. (It's also available as\n\n`vercel install`\n\n(alias `vercel i`\n\n), so `vc i neon`\n\ngets you to the same place.)If you run the command plain, it prompts you for the choices it needs, like the billing plan and region - but if you run it with flags, it skips the prompts entirely, which is what makes it perfect for agents:\n\nThis command would:\n\n- Provision a Neon database (\n[Lakebase Postgres](https://neon.com/docs/postgres/overview)) from the Vercel Marketplace - Connect it to your Vercel project, injecting connection variables like\n`DATABASE_URL`\n\n- Pull those variables into your local environment via\n`vercel env pull`\n\n, so your agent can start using the connection string right away - Install Neon's agent skills from\n`skills.sh`\n\ninto the project, so the agent knows how to work with what it just provisioned (more about this later)\n\n#### On billing and account shape\n\nvercel integration add neon installs the [Vercel-Managed Integration](https://neon.com/docs/guides/vercel-managed-integration). If you don't already have a Neon account, it creates one for you, and billing runs through your Vercel invoice.\n\nIf you already have a Neon account and want to keep billing with Neon, use the [Neon-Managed Integration](https://neon.com/docs/guides/vercel-managed-integration) instead.\n\nThere’s more `integration`\n\nsubcommands you can run without leaving the terminal, e.g.\n\n`vercel integration discover`\n\nbrowses available providers`vercel integration categories`\n\nlists how they're grouped (databases, AI, observability, and so on)`vercel integration guide neon`\n\nprints setup snippets,- and\n`vercel integration open neon`\n\nopens the Neon console\n\n## Preview branches, included\n\nOnce Neon is connected with Preview enabled, [every Vercel Preview Deployment gets its own isolated Neon branch](https://neon.com/blog/neon-vercel-native-integration). A Neon branch is an instant, isolated copy of your backend: same Postgres schema, same data, ready in about a second. Under the hood it starts as a pointer to existing storage - data is only copied when that branch diverges from its parent, so you can spin up many short-lived environments without paying for full copies each time.\n\nThat maps cleanly onto how Vercel already works with PRs. If you push a feature branch, Vercel opens a Preview Deployment, and Neon opens a matching database branch for it - so any tests or migrations all run against that copy. Reviewers hit a real URL with a real database behind it; when the PR ships or the preview goes away, you clean up the branch the same way you'd clean up the deployment.\n\n#### Cleaning up branches\n\nCleanup timing depends on which path you chose. The Vercel-Managed path follows Vercel's deployment retention policy, while the Neon-Managed path can follow Git branch deletion. The details, and a few ways to tighten it up, are in [Managing Vercel preview branch cleanup](https://neon.com/docs/guides/vercel-branch-cleanup).\n\nPS: If you've turned on Managed Better Auth on the production branch, preview deployments also receive `NEON_AUTH_BASE_URL`\n\n, [so auth works in each isolated preview too](https://neon.com/guides/vercel-neon-auth-branching).\n\n## Skills now load automatically\n\nWhen you tell your agent to deploy Neon via Vercel, you’d want your agent to know Neon already and what to do with it. To make sure this is the case, now when you install a Marketplace integration from the CLI, it now also pulls that provider's agent skills from [skills.sh](https://skills.sh/neondatabase/agent-skills):\n\nInstead of guessing and reinventing workflows, your agent will gets Neon's own guidance on how to work with Postgres and the rest of the primitives.\n\nBy the way if you ever want the skills without provisioning anything, you can also install them directly:\n\n## Tell your agent to deploy Neon\n\nAgents are the first-class interface for deploying Neon. There’s a few ways to get Neon context and tooling in front of an agent - the Vercel CLI adds one more:\n\n| Path | Provisions a database? | MCP / tooling | Best when |\n|---|---|---|---|\nVercel CLI `vercel integration add neon` | Yes - on your Vercel project | No MCP setup. Connection vars via `vercel env pull` | You’re working on Vercel |\n| Cursor plugin\n|\n\n`claude plugin install neon@claude-plugins-official`\n\n`npx neon@latest init`\n\nTry it, and if you get stuck, you'll find us in the [Discord](https://neon.com/discord).", "url": "https://wpnews.pro/news/neon-skills-landed-in-the-vercel-cli", "canonical_source": "https://neon.com/blog/neon-skills-landed-in-the-vercel-cli", "published_at": "2026-08-13 18:51:42.317242+00:00", "updated_at": "2026-08-13 18:51:44.285754+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-tools"], "entities": ["Vercel", "Neon", "Lakebase Postgres", "Vercel Marketplace", "Neon-Managed Integration", "Vercel-Managed Integration"], "alternates": {"html": "https://wpnews.pro/news/neon-skills-landed-in-the-vercel-cli", "markdown": "https://wpnews.pro/news/neon-skills-landed-in-the-vercel-cli.md", "text": "https://wpnews.pro/news/neon-skills-landed-in-the-vercel-cli.txt", "jsonld": "https://wpnews.pro/news/neon-skills-landed-in-the-vercel-cli.jsonld"}}