feat(prisma-postgres-setup): cover the Vercel CLI path, env vars, first query and errors

[gregory-boch-prisma]

Why

Vercel's partner guide ("Grow your Vercel integration installs") names the agent skill as the main way to get more CLI installs. It asks that the skill cover setup, environment variables, a first successful request, validation and common errors. Vercel serves prisma-postgres-setup and prisma-orm-setup from the Prisma Marketplace listing, and the CLI installs them when someone runs vercel integration add prisma. Today references/vercel-marketplace.md covers only the v0 flow.

What changed

prisma-postgres-setup/references/vercel-marketplace.md:

• Setup: reuse first (vercel integration list, resource connect). Then vercel integration add prisma/prisma-postgres: read --help for the region values, plan IDs free/starter/pro/business, and terms acceptance in the browser, which an agent can't do. By default the resource connects to production, preview and development, so all three share one database.
• Environment variables: the integration sets DATABASE_URL, POSTGRES_URL and PRISMA_DATABASE_URL. All three hold the direct db.prisma.io endpoint. On older resources PRISMA_DATABASE_URL can be an Accelerate URL. The section covers when to tell the user to move application traffic to pooled.db.prisma.io.
• First request and validation: vercel env pull / vercel env run, the ORM handoff, SELECT 1, redeploying after connecting, and vercel integration list / vercel env ls.
• Plans, billing, backups: a paid plan bills the user's Vercel account, so the agent must ask first. Free has no restorable backup.
• Common errors (7): terms acceptance, env var collisions, DATABASE_URL missing in the CLI, the Accelerate URL in PRISMA_DATABASE_URL, a stale deployment, connection limits, and a shadow database or reset run against the connected database (the last one from a real support case on 2026-10-12).
• The v0 and MCP guidance is unchanged.

prisma-postgres-setup/SKILL.md: the routing row now includes "a Vercel project", and the version goes from 2.0.0 to 2.1.0.

Sources

• Env var names and values: pdp-control-plane services/marketplaces/vercel/utils.ts (buildProvisioningSecrets) and index.ts (provisioning, secret rotation), main at dae59d3e.
• Region values and plan IDs: services/marketplaces/vercel/data/product.ts and data/billing.ts.
• CLI behaviour: vercel.com/docs/cli/integration (updated 2026-09-17), vercel.com/docs/cli/env, and Vercel's KB guide on coding agents and Marketplace integrations.
• Connection limits and pooled vs direct: prisma.io/docs/postgres/database/connection-pooling.

Not verified yet

• No end-to-end run with the Vercel CLI. It isn't authenticated on my machine, and my test team isn't Prisma's. The commands and flags come from Vercel's docs and our integration code. I didn't reproduce any of the errors.
• Whether Prisma Console offers a pooled connection string for a Vercel-managed database.
• AGENTS.md asks for a v0 load check before Marketplace content is released. Not done.

Merge note

#32 also bumps this skill to 2.1.0. Whichever PR merges second should take 2.2.0. The two also touch neighbouring lines of the routing table.

🤖 Generated with Claude Code