marketplace
Vercel Marketplace expert guidance — discovering, installing, and managing third-party integrations via the `vercel integration` CLI. Use when building any app that needs an external capability without a dedicated skill — commerce (stores, storefronts, selling products), payments (checkout, subscriptions, billing), observability/monitoring, messaging/email, search, or CMS — or when discovering, installing, or managing integrations.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 29
- Forks
- 156
01 前言 Front Matter
- name
- marketplace
- chainTo
- [ { "message": "Database/storage integration detected — loading Storage guidance (Neon, Upstash, Supabase, Prisma, Mongo, …), connection pooling, and serverless patterns.", "pattern": "NEON_|POSTGRES_|DATABASE_URL|@neondatabase|@vercel/postgres|@upstash/|@vercel/kv|@supabase/|@prisma/client|\\bmongodb\\b|mongoose|@libsql/|\\bconvex\\b|@vercel/blob", "targetSkill": "vercel-storage" }, { "message": "Auth provider detected — loading Auth guidance (Clerk, Auth0, Descope, Auth.js), middleware setup, and route protection.", "pattern": "CLERK_|@clerk/|clerkMiddleware|@auth0/|AUTH0_|@descope/|next-auth|@auth/|getServerSession", "targetSkill": "auth" }, { "message": "AI usage detected — loading AI guidance for model routing through the AI Gateway, provider/model strings, and streaming.", "pattern": "@ai-sdk/|AI_GATEWAY|generateText|streamText|@openai/|@anthropic-ai/", "targetSkill": "ai-sdk" } ]
- metadata
- { "docs": [ "https://vercel.com/docs/integrations" ], "sitemap": "https://vercel.com/sitemap.xml", "priority": 3, "bashPatterns": [ "\\bvercel\\s+integration\\b", "\\bvercel\\s+integration\\s+add\\b", "\\bvercel\\s+integration\\s+discover\\b" ], "pathPatterns": [ "integration.json" ] }
- retrieval
- { "aliases": [ "vercel integrations", "marketplace", "third party services", "add ons" ], "intents": [ "install integration", "manage marketplace", "add third party service", "discover integrations" ], "entities": [ "Vercel Marketplace", "integration", "vercel integration", "unified billing" ] }
- description
- Vercel Marketplace expert guidance — discovering, installing, and managing third-party integrations via the `vercel integration` CLI. Use when building any app that needs an external capability without a dedicated skill — commerce (stores, storefronts, selling products), payments (checkout, subscriptions, billing), observability/monitoring, messaging/email, search, or CMS — or when discovering, installing, or managing integrations.
03 SKILL.md 正文
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
discoverresult 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> --yes --no-claim(vercel linkfirst if not linked). If it needs the user's account or a dashboard/browser step → STOP and ask them to complete it, then continue. Nevernpm installa 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" buttonmessaging— email, SMS, chat, push notificationsmonitoring— uptime, health checks, alertsobservability— traces, APM, error tracking, metricslogging— log aggregation and searchanalytics— product / usage analyticssearching— site, docs, or product searchcms— blog / content managementflags— feature flagsexperimentation— A/B tests and experimentsvideo— video hosting / streaming / processingagents— AI agents / autonomous task runnerssupport-agent— customer-support agentscode-review— automated code reviewcode-security— code / dependency scanningsecurity— app security (WAF, bot protection)testing— testing / QAweb-automation— scraping / browser automationworkflow— durable workflows / orchestrationdev-tools— developer toolingproductivity— 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 bareadd. - 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> --yes·env ls/env pull --yes·list/update/remove --yes/balance <name>. - Never echo secret values (
env lsshows names only). CI / non-interactive:--yes,--format=json,--no-claim.
Official Documentation
04 同仓库更多 Skills
business-data
暂无简介
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.
workflow
Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
verification
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
vercel-storage
Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
vercel-services
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.