Index of every page on this site: llms.txt
All skills
vercel avatar

/marketplace

@250769d official
by vercelvercel/vercel-plugin340 stars
82
Run it yourself

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.

  • 2 files
  • 9.6 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/vercel/vercel-plugin/marketplace

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈114 tokens for metadata: the name and description. ≈1.9k when used: this file.

Description uses 5.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈449 characters, or 5.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

  1. 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.
  2. Not in the table → take the top relevant discover result for the category.
  3. 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

  1. Categorize — vercel integration categories (read-only). Match the need via the map below.
  2. Discover — vercel integration discover --category <slug> (read-only). Take the top result and provision it (see MUST FOLLOW above).
  3. 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."
  4. Build — vercel env pull --yes, then build the app against the real env vars.

Steps 1–2 need only vercel login, no provider account — 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.
  • Removal: vercel integration resource remove <resource> (alias vercel integration-resource remove / vercel ir rm) deletes the resource permanently; it refuses while projects are connected unless --disconnect-all detaches them first. vercel integration remove <integration> uninstalls the integration and fails while it still has resources. Run either one (with or without --yes) only after the user explicitly approves removing that named resource or integration.
  • Never echo secret values (env ls shows names only). CI / non-interactive: --yes, --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

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 250769d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
Other metadata
metadata
{
  "priority": 3,
  "docs": [
    "https://vercel.com/docs/integrations",
    "https://vercel.com/docs/agent-resources/vercel-plugin"
  ],
  "sitemap": "https://vercel.com/sitemap.xml",
  "pathPatterns": [
    "integration.json"
  ],
  "bashPatterns": [
    "\\bvercel\\s+integration\\b",
    "\\bvercel\\s+integration\\s+add\\b",
    "\\bvercel\\s+integration\\s+discover\\b",
    "\\bvercel\\s+install\\b",
    "\\bvercel\\s+i\\b"
  ]
}
retrieval
{
  "aliases": [
    "vercel integrations",
    "marketplace",
    "third party services",
    "add ons",
    "vercel install"
  ],
  "intents": [
    "install integration",
    "manage marketplace",
    "add third party service",
    "discover integrations"
  ],
  "entities": [
    "Vercel Marketplace",
    "integration",
    "vercel integration",
    "vercel install",
    "unified billing",
    "provider agent skills"
  ]
}
chainTo
[
  {
    "pattern": "NEON_|POSTGRES_|DATABASE_URL|@neondatabase|@vercel/postgres|@upstash/|@vercel/kv|@supabase/|@prisma/client|@prisma/orm-postgres|\\bmongodb\\b|mongoose|@libsql/|\\bconvex\\b|@vercel/blob",
    "targetSkill": "vercel-storage",
    "message": "Database/storage integration detected — loading Storage guidance (Neon, Upstash, Supabase, Prisma Postgres, Mongo, …), connection pooling, and serverless patterns."
  },
  {
    "pattern": "CLERK_|@clerk/|clerkMiddleware|@auth0/|AUTH0_|@descope/|next-auth|@auth/|getServerSession",
    "targetSkill": "auth",
    "message": "Auth provider detected — loading Auth guidance (Clerk, Auth0, Descope, Auth.js), middleware setup, and route protection."
  },
  {
    "pattern": "@ai-sdk/|AI_GATEWAY|generateText|streamText|@openai/|@anthropic-ai/",
    "targetSkill": "ai-sdk",
    "message": "AI usage detected — loading AI guidance for model routing through the AI Gateway, provider/model strings, and streaming."
  }
]

README badge

README badge for vercel/vercel-plugin/marketplace