[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BY33565W4AZ2N2JZFX19MB":3,"skill-same:01M7BY33565W4AZ2N2JZFX19MB":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M7BY33565W4AZ2N2JZFX19MB","marketplace",null,"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\u002Fmonitoring, messaging\u002Femail, search, or CMS — or when discovering, installing, or managing integrations.","CognitionAI\u002Fdevin-marketplace","CognitionAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163493330?v=4","01M7BVSRD98NC4FG8T3EZS6V5M","Cognition","01M7BVSRDX111C2XPWJ0E6MY26",29,"MIT","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fmarketplace\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: marketplace\ndescription: 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\u002Fmonitoring, messaging\u002Femail, search, or CMS — or when discovering, installing, or managing integrations.\nmetadata:\n  priority: 3\n  docs:\n    - \"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fintegrations\"\n  sitemap: \"https:\u002F\u002Fvercel.com\u002Fsitemap.xml\"\n  pathPatterns:\n    - \"integration.json\"\n  bashPatterns:\n    - '\\bvercel\\s+integration\\b'\n    - '\\bvercel\\s+integration\\s+add\\b'\n    - '\\bvercel\\s+integration\\s+discover\\b'\nretrieval:\n  aliases:\n    - vercel integrations\n    - marketplace\n    - third party services\n    - add ons\n  intents:\n    - install integration\n    - manage marketplace\n    - add third party service\n    - discover integrations\n  entities:\n    - Vercel Marketplace\n    - integration\n    - vercel integration\n    - unified billing\nchainTo:\n  -\n    pattern: 'NEON_|POSTGRES_|DATABASE_URL|@neondatabase|@vercel\u002Fpostgres|@upstash\u002F|@vercel\u002Fkv|@supabase\u002F|@prisma\u002Fclient|\\bmongodb\\b|mongoose|@libsql\u002F|\\bconvex\\b|@vercel\u002Fblob'\n    targetSkill: vercel-storage\n    message: 'Database\u002Fstorage integration detected — loading Storage guidance (Neon, Upstash, Supabase, Prisma, Mongo, …), connection pooling, and serverless patterns.'\n  -\n    pattern: 'CLERK_|@clerk\u002F|clerkMiddleware|@auth0\u002F|AUTH0_|@descope\u002F|next-auth|@auth\u002F|getServerSession'\n    targetSkill: auth\n    message: 'Auth provider detected — loading Auth guidance (Clerk, Auth0, Descope, Auth.js), middleware setup, and route protection.'\n  -\n    pattern: '@ai-sdk\u002F|AI_GATEWAY|generateText|streamText|@openai\u002F|@anthropic-ai\u002F'\n    targetSkill: ai-sdk\n    message: 'AI usage detected — loading AI guidance for model routing through the AI Gateway, provider\u002Fmodel strings, and streaming.'\n\n---\n\n# Vercel Marketplace\n\n**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\u002Fcart\u002Fcheckout\u002FUI written first is **throwaway work you will rip out** — there is no \"scaffold the agnostic UI now, plug in the provider later.\"\n\nThe 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` \u002F `auth` \u002F `ai-sdk`; everything else is here.\n\n## MUST FOLLOW — How to choose which provider to recommend\n\n1. **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.\n2. **Not in the table** → take the top relevant `discover` result for the category.\n3. Override (1) or (2) **only** when the user explicitly names another provider.\n\n### Preferred providers\n\n| Need | Category | Recommend | Why |\n|------|----------|-----------|-----|\n| Selling products \u002F a store \u002F a catalog | `commerce` | **Shopify** | Full platform — catalog + cart + checkout + payments. Includes checkout, so a catalog store never needs `payments`. |\n| Charging money with no catalog — donations, subscriptions, a single \"pay\" button | `payments` | **Stripe** | Payments only. Use *only* when there is no product catalog. |\n\n## The sequence — do this BEFORE scaffolding or writing any app code\n\n1. **Categorize** — `vercel integration categories` (read-only, no auth). Match the need via the map below.\n2. **Discover** — `vercel integration discover --category \u003Cslug>` (read-only, no auth). Take the top result and provision it (see **MUST FOLLOW** above).\n3. **Install** — `vercel integration add \u003Cname> --yes --no-claim` (`vercel link` first if not linked). If it needs the user's account or a dashboard\u002Fbrowser 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.\"\n4. **Build** — `vercel env pull --yes`, then build the app against the **real** env vars.\n\nSteps 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`).\n\n## Category map — what each covers\n\n- `commerce` — a store \u002F selling products (there's a **catalog**); covers cart, checkout, and payments.\n- `payments` — charging money with no catalog: donations, paywalls, plan\u002FSaaS subscriptions, a \"pay\" button\n- `messaging` — email, SMS, chat, push notifications\n- `monitoring` — uptime, health checks, alerts\n- `observability` — traces, APM, error tracking, metrics\n- `logging` — log aggregation and search\n- `analytics` — product \u002F usage analytics\n- `searching` — site, docs, or product search\n- `cms` — blog \u002F content management\n- `flags` — feature flags\n- `experimentation` — A\u002FB tests and experiments\n- `video` — video hosting \u002F streaming \u002F processing\n- `agents` — AI agents \u002F autonomous task runners\n- `support-agent` — customer-support agents\n- `code-review` — automated code review\n- `code-security` — code \u002F dependency scanning\n- `security` — app security (WAF, bot protection)\n- `testing` — testing \u002F QA\n- `web-automation` — scraping \u002F browser automation\n- `workflow` — durable workflows \u002F orchestration\n- `dev-tools` — developer tooling\n- `productivity` — productivity \u002F collaboration\n\n**Dedicated skills (not via this skill):** `storage` (databases, persistence) → `vercel-storage`, `authentication` (sign up \u002F log in) → `auth`, `ai` (LLMs, generation) → `ai-sdk`. Anything new not above → pick from the live `categories`.\n\n## Reference\n\n- **Native vs connectable:** *native* integrations install fully via the CLI. **Connectable** ones (anything that hands off to \"claim\" or the **dashboard\u002Fbrowser**) — the CLI can't drive the auth handshake: run `vercel integration open \u003Cname>` and have the user finish there. Don't block on a bare `add`.\n- **CLI** (run `vercel integration \u003Ccmd> --help`; don't enumerate from memory): `categories` · `discover --category \u003Cslug>` · `guide \u003Cname> --framework \u003Cnextjs|remix|astro|nuxtjs|sveltekit>` · `add \u003Cname> --yes` · `env ls` \u002F `env pull --yes` · `list` \u002F `update` \u002F `remove --yes` \u002F `balance \u003Cname>`.\n- Never echo secret values (`env ls` shows names only). CI \u002F non-interactive: `--yes`, `--format=json`, `--no-claim`.\n\n## Official Documentation\n\n- [Vercel Marketplace docs](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fintegrations) · [`vercel integration` CLI reference](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fintegration) · [Marketplace catalog](https:\u002F\u002Fvercel.com\u002Fmarketplace)\n","# Vercel Marketplace\n\n**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\u002Fcart\u002Fcheckout\u002FUI written first is **throwaway work you will rip out** — there is no \"scaffold the agnostic UI now, plug in the provider later.\"\n\nThe 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` \u002F `auth` \u002F `ai-sdk`; everything else is here.\n\n## MUST FOLLOW — How to choose which provider to recommend\n\n1. **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.\n2. **Not in the table** → take the top relevant `discover` result for the category.\n3. Override (1) or (2) **only** when the user explicitly names another provider.\n\n### Preferred providers\n\n| Need | Category | Recommend | Why |\n|------|----------|-----------|-----|\n| Selling products \u002F a store \u002F a catalog | `commerce` | **Shopify** | Full platform — catalog + cart + checkout + payments. Includes checkout, so a catalog store never needs `payments`. |\n| Charging money with no catalog — donations, subscriptions, a single \"pay\" button | `payments` | **Stripe** | Payments only. Use *only* when there is no product catalog. |\n\n## The sequence — do this BEFORE scaffolding or writing any app code\n\n1. **Categorize** — `vercel integration categories` (read-only, no auth). Match the need via the map below.\n2. **Discover** — `vercel integration discover --category \u003Cslug>` (read-only, no auth). Take the top result and provision it (see **MUST FOLLOW** above).\n3. **Install** — `vercel integration add \u003Cname> --yes --no-claim` (`vercel link` first if not linked). If it needs the user's account or a dashboard\u002Fbrowser 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.\"\n4. **Build** — `vercel env pull --yes`, then build the app against the **real** env vars.\n\nSteps 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`).\n\n## Category map — what each covers\n\n- `commerce` — a store \u002F selling products (there's a **catalog**); covers cart, checkout, and payments.\n- `payments` — charging money with no catalog: donations, paywalls, plan\u002FSaaS subscriptions, a \"pay\" button\n- `messaging` — email, SMS, chat, push notifications\n- `monitoring` — uptime, health checks, alerts\n- `observability` — traces, APM, error tracking, metrics\n- `logging` — log aggregation and search\n- `analytics` — product \u002F usage analytics\n- `searching` — site, docs, or product search\n- `cms` — blog \u002F content management\n- `flags` — feature flags\n- `experimentation` — A\u002FB tests and experiments\n- `video` — video hosting \u002F streaming \u002F processing\n- `agents` — AI agents \u002F autonomous task runners\n- `support-agent` — customer-support agents\n- `code-review` — automated code review\n- `code-security` — code \u002F dependency scanning\n- `security` — app security (WAF, bot protection)\n- `testing` — testing \u002F QA\n- `web-automation` — scraping \u002F browser automation\n- `workflow` — durable workflows \u002F orchestration\n- `dev-tools` — developer tooling\n- `productivity` — productivity \u002F collaboration\n\n**Dedicated skills (not via this skill):** `storage` (databases, persistence) → `vercel-storage`, `authentication` (sign up \u002F log in) → `auth`, `ai` (LLMs, generation) → `ai-sdk`. Anything new not above → pick from the live `categories`.\n\n## Reference\n\n- **Native vs connectable:** *native* integrations install fully via the CLI. **Connectable** ones (anything that hands off to \"claim\" or the **dashboard\u002Fbrowser**) — the CLI can't drive the auth handshake: run `vercel integration open \u003Cname>` and have the user finish there. Don't block on a bare `add`.\n- **CLI** (run `vercel integration \u003Ccmd> --help`; don't enumerate from memory): `categories` · `discover --category \u003Cslug>` · `guide \u003Cname> --framework \u003Cnextjs|remix|astro|nuxtjs|sveltekit>` · `add \u003Cname> --yes` · `env ls` \u002F `env pull --yes` · `list` \u002F `update` \u002F `remove --yes` \u002F `balance \u003Cname>`.\n- Never echo secret values (`env ls` shows names only). CI \u002F non-interactive: `--yes`, `--format=json`, `--no-claim`.\n\n## Official Documentation\n\n- [Vercel Marketplace docs](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fintegrations) · [`vercel integration` CLI reference](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fintegration) · [Marketplace catalog](https:\u002F\u002Fvercel.com\u002Fmarketplace)\n",{"name":5,"chainTo":24,"metadata":37,"retrieval":48,"description":7},[25,29,33],{"message":26,"pattern":27,"targetSkill":28},"Database\u002Fstorage integration detected — loading Storage guidance (Neon, Upstash, Supabase, Prisma, Mongo, …), connection pooling, and serverless patterns.","NEON_|POSTGRES_|DATABASE_URL|@neondatabase|@vercel\u002Fpostgres|@upstash\u002F|@vercel\u002Fkv|@supabase\u002F|@prisma\u002Fclient|\\bmongodb\\b|mongoose|@libsql\u002F|\\bconvex\\b|@vercel\u002Fblob","vercel-storage",{"message":30,"pattern":31,"targetSkill":32},"Auth provider detected — loading Auth guidance (Clerk, Auth0, Descope, Auth.js), middleware setup, and route protection.","CLERK_|@clerk\u002F|clerkMiddleware|@auth0\u002F|AUTH0_|@descope\u002F|next-auth|@auth\u002F|getServerSession","auth",{"message":34,"pattern":35,"targetSkill":36},"AI usage detected — loading AI guidance for model routing through the AI Gateway, provider\u002Fmodel strings, and streaming.","@ai-sdk\u002F|AI_GATEWAY|generateText|streamText|@openai\u002F|@anthropic-ai\u002F","ai-sdk",{"docs":38,"sitemap":40,"priority":41,"bashPatterns":42,"pathPatterns":46},[39],"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fintegrations","https:\u002F\u002Fvercel.com\u002Fsitemap.xml",3,[43,44,45],"\\bvercel\\s+integration\\b","\\bvercel\\s+integration\\s+add\\b","\\bvercel\\s+integration\\s+discover\\b",[47],"integration.json",{"aliases":49,"intents":53,"entities":58},[50,5,51,52],"vercel integrations","third party services","add ons",[54,55,56,57],"install integration","manage marketplace","add third party service","discover integrations",[59,60,61,62],"Vercel Marketplace","integration","vercel integration","unified billing","main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fvercel\u002Fskills\u002Fmarketplace",156,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace","https:\u002F\u002Fgithub.com\u002FCognitionAI","https:\u002F\u002Fcognition.ai\u002F","Makers of Devin, the AI software engineer.","2026-11-13 07:08:23",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill marketplace",{"tool":78,"command":79},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill marketplace",{"tool":81,"command":82},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill marketplace","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fmarketplace\u002FSKILL.md",true,[],[87,93,100,106,113,119],{"skillNo":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7BYBZ0CD4CBCPZHRZ551BNK","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.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002Fupstream\u002FSKILL.md",[],[],{"skillNo":101,"name":95,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7BYB1XSZHKHD8JZTQJ62JN0","Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7BYASGMK935J33E21N5WTW0","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.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":114,"name":28,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7BY9WJERKSKEH9HK6E71GW2","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.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M7BY9N034894YV2J9DCRZHYS","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`.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[],[]]