What problem does it solve? Building an app that needs an external capability (commerce, payments, email, monitoring, search, CMS) often leads to hand-written scaffolding that gets thrown away once a real provider is chosen. This Skill enforces the correct order — categorize, discover, install, then build — so the Vercel Marketplace integration provisions the backend, environment variables, and unified billing before any app code is written. ## Core Features & Use Cases - Guided provider selection: Recommends preferred providers (Shopify for commerce, Stripe for payments) and falls back to the top vercel integration discover result for other categories. - CLI-driven provisioning: Runs vercel integration categories, discover, add --yes --no-claim, and vercel env pull to install integrations with auto-configured env vars and unified billing. - Category mapping: Maps needs like messaging, observability, logging, analytics, searching, cms, flags, and video to Marketplace categories, while routing databases, auth, and AI to dedicated skills. - Use Case: A user asks to build an online store. The Skill runs vercel integration discover --category commerce, installs Shopify via the CLI, pulls the real env vars, and only then scaffolds the storefront against the provisioned catalog, cart, and checkout. ## Quick Start Ask the assistant to discover and install a Vercel Marketplace integration for your app's need, for example adding a commerce backend before scaffolding a storefront.
