Marketplace

This skill handles Vercel's integration marketplace, the system that lets you wire third-party services like Neon, Clerk, or Datadog into your projects with one command. It covers discovery, installation via `vercel integration add`, and the auto-provisioned environment variables that get injected without manual `.env` wrangling. The guidance includes smart chaining: if you install Neon it loads storage patterns, if you add Clerk it switches to auth middleware setup. It also covers building your own integrations with manifests, webhooks, and resource provisioning. The 1–3 minute delay after database installs is real and worth remembering before you start debugging phantom connection errors.

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

View on GitHub

Install

$ npx -y skills add vercel/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.