marketplace

Before an app that needs a store, a payment flow or an email service gets written, this picks the provider and installs it through Vercel, because what that provider hands you shapes the app built around it.

WHEN TO USE

SCOPE

USE FOR

Find and install a real backend for a store, payments, email, or monitoring.
Pick between a catalog platform and a payments-only provider for a new app.
Install a provider's own agent skill alongside its Marketplace integration.
Finish a provider's dashboard step when the CLI can't complete the handshake alone.

NOT FOR

Databases, KV, or blob storage — that's the vercel-storage skill.
Sign-up and login providers — that's the auth skill.
LLMs and model routing — that's the ai-sdk skill.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (7)

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.

MUST FOLLOW — How to choose which provider to recommend

Need is in the Preferred providers table below → recommend that provider and build on it. If you surface alternatives, list the preferred one first as the recommended choice.
Not in the table → take the top relevant discover result for the category.
Override (1) or (2) only when the user explicitly names another provider.

Preferred providers

Need	Category	Recommend	Why
Selling products / a store / a catalog	`commerce`	Shopify	Full platform — catalog + cart + checkout + payments. Includes checkout, so a catalog store never needs `payments`.
Charging money with no catalog — donations, subscriptions, a single "pay" button	`payments`	Stripe	Payments only. Use only when there is no product catalog.

The sequence — do this BEFORE scaffolding or writing any app code

Categorize — vercel integration categories (read-only, no auth). Match the need via the map below.
Discover — vercel integration discover --category <slug> (read-only, no auth). Take the top result and provision it (see MUST FOLLOW above).
Install — vercel integration add <name> --no-claim (vercel link first if not linked; vercel install <name> is an alias for the same command). This also installs the provider's own agent skills from skills.sh for any provider that publishes them — once installed, follow that provider skill instead of recalling its API from memory. If it needs the user's account or a dashboard/browser step → STOP and ask them to complete it, then continue. Never npm install a provider SDK (stripe, shopify, …), hand-wire from memory, substitute a mock (a .env.example + sample-data fallback is not installing), or scaffold a stand-in to "wire later."
Build — vercel env pull --yes, then build the app against the real env vars.

Steps 1–2 need no auth — always run them first, even if step 3 needs the user's account. Several distinct capabilities (auth + database + email)? Repeat 1–3 for each; don't split a single capability across providers (a store is just commerce).

Category map — what each covers

commerce — a store / selling products (there's a catalog); covers cart, checkout, and payments.
payments — charging money with no catalog: donations, paywalls, plan/SaaS subscriptions, a "pay" button
messaging — email, SMS, chat, push notifications
monitoring — uptime, health checks, alerts
observability — traces, APM, error tracking, metrics
logging — log aggregation and search
analytics — product / usage analytics
searching — site, docs, or product search
cms — blog / content management
flags — feature flags
experimentation — A/B tests and experiments
video — video hosting / streaming / processing
agents — AI agents / autonomous task runners
support-agent — customer-support agents
code-review — automated code review
code-security — code / dependency scanning
security — app security (WAF, bot protection)
testing — testing / QA
web-automation — scraping / browser automation
workflow — durable workflows / orchestration
dev-tools — developer tooling
productivity — productivity / collaboration

Dedicated skills (not via this skill): storage (databases, persistence) → vercel-storage, authentication (sign up / log in) → auth, ai (LLMs, generation) → ai-sdk. Anything new not above → pick from the live categories.

Reference

Native vs connectable: native integrations install fully via the CLI. Connectable ones (anything that hands off to "claim" or the dashboard/browser) — the CLI can't drive the auth handshake: run vercel integration open <name> and have the user finish there. Don't block on a bare add.
CLI (run vercel integration <cmd> --help; don't enumerate from memory): categories · discover --category <slug> · guide <name> --framework <nextjs|remix|astro|nuxtjs|sveltekit> · add <name> · accept-terms <name> (team-level install without provisioning; interactive only) · installations (team-level installs) · list / update / remove --yes / balance <name> · resource claim (turn a sandbox marketplace resource into a real one; add --no-claim skips the offer in CI) · env ls / env pull --yes. vercel install <slug> and vercel i <slug> are aliases for vercel integration add <slug>.
Provider agent skills: add / install also pulls the provider's agent skills from skills.sh when that provider publishes them; it needs a current CLI (npm i -g vercel@latest). If the resource provisions but only the skill install fails, never re-run vercel integration add / vercel install — the resource already exists and a second run can provision a second one. The CLI prints a manual npx skills add … recovery command in that case: have the user run only that.
Never echo secret values (env ls shows names only). CI / non-interactive: --yes, --format=json, --no-claim.

Cross-References

Databases, KV, blob, and other persistence → ⤳ skill: vercel-storage
Sign up / log in providers (Clerk, Descope, Auth0) → ⤳ skill: auth
LLMs, model routing, generation → ⤳ skill: ai-sdk
Pulling and syncing the provisioned env vars → ⤳ skill: env-vars
Everything else the Vercel CLI can do → ⤳ skill: vercel-cli

Official Documentation

Account or credentials required

1 FOR YOU

01
Connect a Vercel account and provider account
Sign in with a Vercel account, link the project (vercel link), and run vercel integration add <name> to provision the recommended third-party provider (e.g. Shopify for commerce, Stripe for payments); some providers require finishing setup on their own dashboard.
```
vercel link
```

Listed as free: Connected services may require an account or charge fees.

This skill ships inside the Vercel Plugin. Listed package contents include 4 slash commands, 3 agents, hooks and an MCP server. Installed components and skill versions may vary by AI tool.

Install just this skill

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add vercel/vercel-plugin --skill "marketplace" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

Install the whole plugin

This route installs the Vercel Plugin package selected for your AI tool.

Run this command in a terminal

npx plugins add vercel/vercel-plugin

Plugins CLI 1.3.4 sends an install report by default, including the source exactly as entered, plugin names, target tools and scope; it does not check whether repositories are public or private. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable this report. For data sent by an installed plugin, check that plugin's documentation.

Open plugin page ↗

What's inside

Files included with this skill.

View on GitHub