Marketplace

This covers the Vercel Marketplace integration system: discovering third-party services through the CLI, installing them with `vercel integration add`, and letting Vercel auto-provision environment variables so you don't manually juggle credentials. It handles the one-click setup flow for databases like Neon, auth providers like Clerk, and monitoring tools like Datadog, plus the unified billing model where everything shows up on one invoice. The guidance includes the integration build path if you're publishing your own service to the marketplace. Worth noting the 1–3 minute provisioning delay after installing database integrations, which trips people up when connection strings aren't instantly live. Chains out to auth and storage skills when it detects provider-specific patterns in your code.

skills.sh installs: 208
GitHub stars: 183
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add vercel-labs/vercel-plugin --skill marketplace --agent claude-code

Installs into .claude/skills of the current project.

Files

Vercel Marketplace

Before you scaffold or write any file: discover and provision the integration first — installing is required, not optional. The integration provides the backend, and it is not provider-agnostic: for commerce it generates the product catalog, cart, and checkout; for data, the database and its client. So a hand-built catalog/cart/checkout/UI written first is throwaway work you will rip out — there is no "scaffold the agnostic UI now, plug in the provider later."

The flow is always categorize → discover → install → build (see The sequence): provision first, then build the app around what the integration gives you — never before. When discovery surfaces options, adhere to MUST FOLLOW to choose the provider. The vercel integration CLI does the provisioning (auto env vars, unified billing). Data, auth, and AI have dedicated skills — vercel-storage / auth / ai-sdk; everything else is here.