[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVWC1J9V6Q3M12AXR9MEKF":3,"skill-same:01M7CVWC1J9V6Q3M12AXR9MEKF":112},{"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":83,"commitSha":84,"skillDirectory":85,"forksCount":14,"repositoryHtmlUrl":86,"repositoryHomepageUrl":87,"ownerHtmlUrl":88,"ownerBlogUrl":89,"ownerDescription":90,"updatedAt":91,"install":92,"resources":105},"01M7CVWC1J9V6Q3M12AXR9MEKF","vercel-cli",null,"Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, managing domains, or interacting with the Vercel platform from the command line.","realsudarshan\u002FSD-skill","realsudarshan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128029723?v=4","01M7CTP2JEKQ9KBJ51NRZ2777Z","Sudarshan Dhakal","01M7CTP2JYR2PRY3BWGA30HX7J",0,"MIT","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Fofficial-openai\u002Fopenai-local-vercel-vercel-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-cli\ndescription: Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, managing domains, or interacting with the Vercel platform from the command line.\nmetadata:\n  priority: 4\n  docs:\n    - \"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\"\n  sitemap: \"https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml\"\n  pathPatterns:\n    - 'vercel.json'\n    - 'vercel.ts'\n    - '.vercel\u002F**'\n    - '.vercelignore'\n    - 'now.json'\n  bashPatterns:\n    - '^\\s*vercel(?:\\s|$)'\n    - '^\\s*vc(?:\\s|$)'\n    - '\\bnpx\\s+vercel\\b'\n    - '\\bpnpm\\s+dlx\\s+vercel\\b'\n    - '\\bbunx\\s+vercel\\b'\n    - '\\byarn\\s+dlx\\s+vercel\\b'\n    - '\\bnpx\\s+@vercel\u002Fconfig\\b'\n  promptSignals:\n    phrases:\n      - \"check deployment\"\n      - \"check deploy\"\n      - \"deployment status\"\n      - \"deploy status\"\n      - \"vercel logs\"\n      - \"deployment logs\"\n      - \"deploy logs\"\n      - \"vercel inspect\"\n      - \"is it deployed\"\n      - \"deploy failing\"\n      - \"deploy failed\"\n      - \"deployment error\"\n      - \"check vercel\"\n      - \"vercel status\"\n    allOf:\n      - [check, deployment]\n      - [check, deploy]\n      - [vercel, status]\n      - [vercel, logs]\n      - [deploy, error]\n      - [deploy, failed]\n      - [deploy, stuck]\n    anyOf:\n      - \"deployment\"\n      - \"deploy\"\n      - \"vercel\"\n      - \"production\"\n    noneOf:\n      - \"terraform\"\n      - \"aws deploy\"\n      - \"heroku\"\n    minScore: 6\n---\n\n# Vercel CLI\n\nYou are an expert in the Vercel CLI v50.28.0 (`vercel` or `vc`). The CLI is the primary way to manage Vercel projects from the terminal.\n\n## Installation\n\n```bash\nnpm i -g vercel\n```\n\n## Login\n\nThe CLI uses an **OAuth 2.0 Device Flow** for authentication.\n\n```bash\nvercel login\n```\n\n> **Deprecation notice**: Email-based login (`vercel login your@email.com`) and the flags `--github`, `--gitlab`, `--bitbucket`, `--oob` were removed February 26, 2026. The `team` method (SAML-based login) remains supported until June 1, 2026, then will also be removed.\n\n## Core Commands\n\n### Deployment\n\n```bash\n# Preview deployment (from project root)\nvercel\n\n# Production deployment\nvercel --prod\n\n# Build locally, deploy build output only\nvercel build\nvercel deploy --prebuilt\n\n# Build for production (uses production env vars)\nvercel build --prod\nvercel deploy --prebuilt --prod\n\n# Force a new deployment (skip cache)\nvercel --force\n\n# Promote a preview deployment to production\nvercel promote \u003Cdeployment-url>\n\n# Rollback to previous production deployment\nvercel rollback\n```\n\n### Development\n\n```bash\n# Start local dev server with Vercel features\nvercel dev\n\n# Link current directory to a Vercel project\nvercel link\n\n# Deterministic non-interactive link (recommended for bootstrap\u002Fautomation)\nvercel link --yes --project \u003Cname-or-id> --scope \u003Cteam>\n\n# Pull environment variables and project settings\nvercel pull\n\n# Pull specific environment\nvercel pull --environment=production\n\n# Open linked project in the Vercel Dashboard\nvercel open\n```\n\n### Deterministic Project Linking (Recommended)\n\nPrefer explicit non-interactive linking for bootstrap and automation:\n\n```bash\nvercel link --yes --project \u003Cname-or-id> --scope \u003Cteam>\n```\n\nThis is more reliable than interactive prompt-driven linking, which can pick the wrong project or team in multi-account setups. If there is any ambiguity, run `vercel open` to confirm the dashboard project, then relink with explicit `--project` and `--scope`.\n\n### Environment Variables\n\n```bash\n# List all environment variables\nvercel env ls\n\n# Add an environment variable\nvercel env add MY_VAR\n\n# Add for specific environments\nvercel env add MY_VAR production\nvercel env add MY_VAR preview development\n\n# Add branch-scoped variable\nvercel env add MY_VAR preview --branch=feature-x\n\n# Add sensitive (write-only) variable\nvercel env add MY_SECRET --sensitive\n\n# Remove an environment variable\nvercel env rm MY_VAR\n\n# Pull all env vars to .env.local\nvercel env pull\nvercel env pull .env.production.local --environment=production\n```\n\n### Logs & Inspection\n\nThe `vercel logs` command (rebuilt February 2026) supports **historical log querying** and uses **git context by default** â€” it automatically scopes logs to your current repository when run from a project directory.\n\n```bash\n# View runtime\u002Ffunction logs (real-time)\nvercel logs \u003Cdeployment-url>\n\n# Follow logs in real-time (streaming mode)\nvercel logs \u003Cdeployment-url> --follow\n\n# Query historical logs (no longer limited to live-only)\nvercel logs --since 24h\nvercel logs --since 7d\n\n# Filter by time range\nvercel logs \u003Cdeployment-url> --since 1h\nvercel logs \u003Cdeployment-url> --since 30m\n\n# Filter by log level\nvercel logs \u003Cdeployment-url> --level error\nvercel logs \u003Cdeployment-url> --level warning\n\n# Filter by deployment ID, request ID, or arbitrary string\nvercel logs --deployment-id dpl_xxxxx\nvercel logs --request-id req_xxxxx\nvercel logs --query \"TypeError\"\n\n# Output as JSON (for piping to jq or other tools)\nvercel logs \u003Cdeployment-url> --json\n\n# Combine filters: stream errors from the last hour as JSON\nvercel logs \u003Cdeployment-url> --follow --since 1h --level error --json\n\n# Inspect a deployment (build details, metadata, function list)\nvercel inspect \u003Cdeployment-url>\n\n# List recent deployments\nvercel ls\n```\n\n> **Note:** `vercel logs` shows runtime request logs only. For build output, use\n> `vercel inspect \u003Cdeployment-url>` or view build logs at `https:\u002F\u002Fvercel.com\u002F{team}\u002F{project}\u002Fdeployments` â†’ select deployment â†’ **Build Logs**.\n>\n> **Drains and advanced observability:** Log drains, trace export, and analytics data forwarding are\n> configured via the Vercel Dashboard at `https:\u002F\u002Fvercel.com\u002Fdashboard\u002F{team}\u002F~\u002Fsettings\u002Flog-drains` or REST API (`\u002Fv1\u002Fdrains`), not the CLI. See `â¤³ skill: observability`\n> for drain setup, payload schemas, and signature verification.\n\n### Domains\n\n```bash\n# List domains\nvercel domains ls\n\n# Add a domain to a project\nvercel domains add example.com\n\n# Remove a domain\nvercel domains rm example.com\n```\n\n### DNS\n\n```bash\n# List DNS records\nvercel dns ls example.com\n\n# Add a DNS record\nvercel dns add example.com @ A 1.2.3.4\n```\n\n### Teams\n\n```bash\n# List teams\nvercel teams ls\n\n# Switch to a team\nvercel teams switch my-team\n```\n\n### Cache Management\n\n```bash\n# Purge all cache (CDN + Data cache) for current project\nvercel cache purge\n\n# Purge only CDN cache\nvercel cache purge --type cdn\n\n# Purge only Data cache\nvercel cache purge --type data\n\n# Purge without confirmation prompt\nvercel cache purge --yes\n\n# Invalidate by tag (stale-while-revalidate)\nvercel cache invalidate --tag blog-posts\n\n# Invalidate multiple tags\nvercel cache invalidate --tag blog-posts,user-profiles,homepage\n\n# Hard delete by tag (blocks until revalidated â€” use with caution)\nvercel cache dangerously-delete --tag blog-posts\n\n# Hard delete with revalidation deadline (deletes only if not accessed within N seconds)\nvercel cache dangerously-delete --tag blog-posts --revalidation-deadline-seconds 3600\n\n# Invalidate cached image transformations by source path\nvercel cache invalidate --srcimg \u002Fapi\u002Favatar\u002F1\n\n# Hard delete cached image transformations\nvercel cache dangerously-delete --srcimg \u002Fapi\u002Favatar\u002F1\n```\n\n**Key distinction:** `invalidate` serves STALE and revalidates in the background. `dangerously-delete` serves MISS and blocks while revalidating. Prefer `invalidate` unless you need immediate freshness.\n\n**Note:** `--tag` and `--srcimg` cannot be used together.\n\n### MCP Server Integration\n\n```bash\n# Initialize global MCP client configuration for your Vercel account\nvercel mcp\n\n# Set up project-specific MCP access for the linked project\nvercel mcp --project\n```\n\nThe `vercel mcp` command links your local MCP client configuration to a Vercel Project. It generates connection details so AI agents and tools can call your MCP endpoints deployed on Vercel securely.\n\n### Programmatic Configuration (`@vercel\u002Fconfig`)\n\n```bash\n# Compile vercel.ts to JSON (stdout)\nnpx @vercel\u002Fconfig compile\n\n# Validate configuration and show summary\nnpx @vercel\u002Fconfig validate\n\n# Generate vercel.json locally for development\nnpx @vercel\u002Fconfig generate\n```\n\nUse `vercel.ts` (or `.js`, `.mjs`, `.cjs`, `.mts`) instead of `vercel.json` for type-safe, dynamic project configuration. Only one config file per project â€” `vercel.json` or `vercel.ts`, not both.\n\n> **Note:** Legacy `now.json` support will be removed on March 31, 2026. Rename to `vercel.json` (no content changes needed).\n\n### Marketplace Integrations\n\nAuto-provisioning is the default for `vercel integration add` â€” the CLI automatically creates resources and sets environment variables without extra prompts.\n\n```bash\n# List installed integrations\nvercel integration list\n\n# Add an integration (auto-provisions env vars by default)\nvercel integration add neon\n\n# Open an integration's dashboard\nvercel integration open neon\n\n# Remove an integration\nvercel integration remove neon\n```\n\n#### Agent-Optimized: `discover` and `guide`\n\nAI agents can autonomously discover, install, and retrieve setup instructions for Marketplace integrations (added March 2026):\n\n```bash\n# Search the integration catalog (returns JSON for automation)\nvercel integration discover --format=json\n\n# Search with a keyword filter\nvercel integration discover database --format=json\n\n# Get agent-friendly setup guide with code snippets\nvercel integration guide neon\n\n# Full workflow: discover â†’ add â†’ guide\nvercel integration discover storage --format=json\nvercel integration add neon\nvercel integration guide neon\n```\n\n- `discover` â€” Searches the Vercel Marketplace catalog. Use `--format=json` for non-interactive output suitable for scripting and agent pipelines.\n- `guide \u003Cname>` â€” Returns getting-started documentation in agent-friendly markdown: environment variables, SDK setup, and code snippets.\n- Human-in-the-loop safety: the CLI prompts for developer confirmation when accepting Terms of Service.\n\n> Full subcommands: `discover`, `guide`, `add`, `list` (alias `ls`), `balance`, `open`, `remove`.\n\n### Project-Level Routing (No Redeploy)\n\nCreate and update routing rules â€” headers, rewrites, redirects â€” without building a new deployment. Rules take effect instantly.\n\nAvailable via dashboard (CDN tab), API, CLI, and Vercel SDK. Project-level routes run after bulk redirects and before deployment config routes.\n\n### Feature Flags\n\n```bash\n# Create a feature flag\nvercel flags add redesigned-checkout --kind boolean --description \"New checkout flow\"\n\n# List SDK keys\nvercel flags sdk-keys ls\n\n# Enable\u002Fdisable, archive, and manage flags from CLI\nvercel flags --help\n```\n\nSee `â¤³ skill: vercel-flags` for full flag configuration and adapter patterns.\n\n### Direct API Access\n\nThe `vercel api` command (added January 2026) gives direct access to the full Vercel REST API from the terminal. Designed for AI agents â€” call Vercel APIs with no additional configuration.\n\n```bash\n# Call any Vercel REST API endpoint\nvercel api GET \u002Fv9\u002Fprojects\nvercel api GET \u002Fv13\u002Fdeployments\nvercel api POST \u002Fv9\u002Fprojects\u002F:id\u002Fenv --body '{\"key\":\"MY_VAR\",\"value\":\"val\",\"target\":[\"production\"]}'\n\n# Pipe JSON output to jq\nvercel api GET \u002Fv9\u002Fprojects | jq '.[].name'\n```\n\n### Metrics\n\n```bash\n# Query project metrics (rich text output with sparklines)\nvercel metrics\n\n# Raw values for scripting\nvercel metrics --raw-values\n```\n\n## CI\u002FCD Integration\n\nRequired environment variables for CI:\n```bash\nVERCEL_TOKEN=\u003Cyour-token>\nVERCEL_ORG_ID=\u003Corg-id>\nVERCEL_PROJECT_ID=\u003Cproject-id>\n```\n\n### GitHub Actions Example\n\n```yaml\n- name: Deploy to Vercel\n  run: |\n    vercel pull --yes --environment=production --token=${{ secrets.VERCEL_TOKEN }}\n    vercel build --prod --token=${{ secrets.VERCEL_TOKEN }}\n    vercel deploy --prebuilt --prod --token=${{ secrets.VERCEL_TOKEN }}\n```\n\n## Global Options\n\n| Flag | Purpose |\n|------|---------|\n| `--token` | Authentication token (for CI) |\n| `--cwd \u003Cdir>` | Working directory |\n| `--debug` \u002F `-d` | Verbose output |\n| `--yes` \u002F `-y` | Skip confirmation prompts |\n| `--scope \u003Cteam>` | Execute as a team |\n\n## Common Workflows\n\n### First-Time Setup\n```bash\nvercel link          # Connect to Vercel project\nvercel env pull      # Get environment variables\nvercel dev           # Start local dev\n```\n\n### Deploy from CI\n```bash\nvercel pull --yes --environment=production --token=$TOKEN\nvercel build --prod --token=$TOKEN\nvercel deploy --prebuilt --prod --token=$TOKEN\n```\n\n### Quick Preview\n```bash\nvercel               # Creates preview deployment, returns URL\n```\n\n## Official Documentation\n\n- [Vercel CLI](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli)\n- [Cache Management](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fcache)\n- [MCP Integration](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fmcp)\n- [Deployments](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fdeployments)\n- [REST API](https:\u002F\u002Fvercel.com\u002Fdocs\u002Frest-api\u002Freference)\n- [GitHub: Vercel CLI](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fvercel)\n","# Vercel CLI\n\nYou are an expert in the Vercel CLI v50.28.0 (`vercel` or `vc`). The CLI is the primary way to manage Vercel projects from the terminal.\n\n## Installation\n\n```bash\nnpm i -g vercel\n```\n\n## Login\n\nThe CLI uses an **OAuth 2.0 Device Flow** for authentication.\n\n```bash\nvercel login\n```\n\n> **Deprecation notice**: Email-based login (`vercel login your@email.com`) and the flags `--github`, `--gitlab`, `--bitbucket`, `--oob` were removed February 26, 2026. The `team` method (SAML-based login) remains supported until June 1, 2026, then will also be removed.\n\n## Core Commands\n\n### Deployment\n\n```bash\n# Preview deployment (from project root)\nvercel\n\n# Production deployment\nvercel --prod\n\n# Build locally, deploy build output only\nvercel build\nvercel deploy --prebuilt\n\n# Build for production (uses production env vars)\nvercel build --prod\nvercel deploy --prebuilt --prod\n\n# Force a new deployment (skip cache)\nvercel --force\n\n# Promote a preview deployment to production\nvercel promote \u003Cdeployment-url>\n\n# Rollback to previous production deployment\nvercel rollback\n```\n\n### Development\n\n```bash\n# Start local dev server with Vercel features\nvercel dev\n\n# Link current directory to a Vercel project\nvercel link\n\n# Deterministic non-interactive link (recommended for bootstrap\u002Fautomation)\nvercel link --yes --project \u003Cname-or-id> --scope \u003Cteam>\n\n# Pull environment variables and project settings\nvercel pull\n\n# Pull specific environment\nvercel pull --environment=production\n\n# Open linked project in the Vercel Dashboard\nvercel open\n```\n\n### Deterministic Project Linking (Recommended)\n\nPrefer explicit non-interactive linking for bootstrap and automation:\n\n```bash\nvercel link --yes --project \u003Cname-or-id> --scope \u003Cteam>\n```\n\nThis is more reliable than interactive prompt-driven linking, which can pick the wrong project or team in multi-account setups. If there is any ambiguity, run `vercel open` to confirm the dashboard project, then relink with explicit `--project` and `--scope`.\n\n### Environment Variables\n\n```bash\n# List all environment variables\nvercel env ls\n\n# Add an environment variable\nvercel env add MY_VAR\n\n# Add for specific environments\nvercel env add MY_VAR production\nvercel env add MY_VAR preview development\n\n# Add branch-scoped variable\nvercel env add MY_VAR preview --branch=feature-x\n\n# Add sensitive (write-only) variable\nvercel env add MY_SECRET --sensitive\n\n# Remove an environment variable\nvercel env rm MY_VAR\n\n# Pull all env vars to .env.local\nvercel env pull\nvercel env pull .env.production.local --environment=production\n```\n\n### Logs & Inspection\n\nThe `vercel logs` command (rebuilt February 2026) supports **historical log querying** and uses **git context by default** â€” it automatically scopes logs to your current repository when run from a project directory.\n\n```bash\n# View runtime\u002Ffunction logs (real-time)\nvercel logs \u003Cdeployment-url>\n\n# Follow logs in real-time (streaming mode)\nvercel logs \u003Cdeployment-url> --follow\n\n# Query historical logs (no longer limited to live-only)\nvercel logs --since 24h\nvercel logs --since 7d\n\n# Filter by time range\nvercel logs \u003Cdeployment-url> --since 1h\nvercel logs \u003Cdeployment-url> --since 30m\n\n# Filter by log level\nvercel logs \u003Cdeployment-url> --level error\nvercel logs \u003Cdeployment-url> --level warning\n\n# Filter by deployment ID, request ID, or arbitrary string\nvercel logs --deployment-id dpl_xxxxx\nvercel logs --request-id req_xxxxx\nvercel logs --query \"TypeError\"\n\n# Output as JSON (for piping to jq or other tools)\nvercel logs \u003Cdeployment-url> --json\n\n# Combine filters: stream errors from the last hour as JSON\nvercel logs \u003Cdeployment-url> --follow --since 1h --level error --json\n\n# Inspect a deployment (build details, metadata, function list)\nvercel inspect \u003Cdeployment-url>\n\n# List recent deployments\nvercel ls\n```\n\n> **Note:** `vercel logs` shows runtime request logs only. For build output, use\n> `vercel inspect \u003Cdeployment-url>` or view build logs at `https:\u002F\u002Fvercel.com\u002F{team}\u002F{project}\u002Fdeployments` â†’ select deployment â†’ **Build Logs**.\n>\n> **Drains and advanced observability:** Log drains, trace export, and analytics data forwarding are\n> configured via the Vercel Dashboard at `https:\u002F\u002Fvercel.com\u002Fdashboard\u002F{team}\u002F~\u002Fsettings\u002Flog-drains` or REST API (`\u002Fv1\u002Fdrains`), not the CLI. See `â¤³ skill: observability`\n> for drain setup, payload schemas, and signature verification.\n\n### Domains\n\n```bash\n# List domains\nvercel domains ls\n\n# Add a domain to a project\nvercel domains add example.com\n\n# Remove a domain\nvercel domains rm example.com\n```\n\n### DNS\n\n```bash\n# List DNS records\nvercel dns ls example.com\n\n# Add a DNS record\nvercel dns add example.com @ A 1.2.3.4\n```\n\n### Teams\n\n```bash\n# List teams\nvercel teams ls\n\n# Switch to a team\nvercel teams switch my-team\n```\n\n### Cache Management\n\n```bash\n# Purge all cache (CDN + Data cache) for current project\nvercel cache purge\n\n# Purge only CDN cache\nvercel cache purge --type cdn\n\n# Purge only Data cache\nvercel cache purge --type data\n\n# Purge without confirmation prompt\nvercel cache purge --yes\n\n# Invalidate by tag (stale-while-revalidate)\nvercel cache invalidate --tag blog-posts\n\n# Invalidate multiple tags\nvercel cache invalidate --tag blog-posts,user-profiles,homepage\n\n# Hard delete by tag (blocks until revalidated â€” use with caution)\nvercel cache dangerously-delete --tag blog-posts\n\n# Hard delete with revalidation deadline (deletes only if not accessed within N seconds)\nvercel cache dangerously-delete --tag blog-posts --revalidation-deadline-seconds 3600\n\n# Invalidate cached image transformations by source path\nvercel cache invalidate --srcimg \u002Fapi\u002Favatar\u002F1\n\n# Hard delete cached image transformations\nvercel cache dangerously-delete --srcimg \u002Fapi\u002Favatar\u002F1\n```\n\n**Key distinction:** `invalidate` serves STALE and revalidates in the background. `dangerously-delete` serves MISS and blocks while revalidating. Prefer `invalidate` unless you need immediate freshness.\n\n**Note:** `--tag` and `--srcimg` cannot be used together.\n\n### MCP Server Integration\n\n```bash\n# Initialize global MCP client configuration for your Vercel account\nvercel mcp\n\n# Set up project-specific MCP access for the linked project\nvercel mcp --project\n```\n\nThe `vercel mcp` command links your local MCP client configuration to a Vercel Project. It generates connection details so AI agents and tools can call your MCP endpoints deployed on Vercel securely.\n\n### Programmatic Configuration (`@vercel\u002Fconfig`)\n\n```bash\n# Compile vercel.ts to JSON (stdout)\nnpx @vercel\u002Fconfig compile\n\n# Validate configuration and show summary\nnpx @vercel\u002Fconfig validate\n\n# Generate vercel.json locally for development\nnpx @vercel\u002Fconfig generate\n```\n\nUse `vercel.ts` (or `.js`, `.mjs`, `.cjs`, `.mts`) instead of `vercel.json` for type-safe, dynamic project configuration. Only one config file per project â€” `vercel.json` or `vercel.ts`, not both.\n\n> **Note:** Legacy `now.json` support will be removed on March 31, 2026. Rename to `vercel.json` (no content changes needed).\n\n### Marketplace Integrations\n\nAuto-provisioning is the default for `vercel integration add` â€” the CLI automatically creates resources and sets environment variables without extra prompts.\n\n```bash\n# List installed integrations\nvercel integration list\n\n# Add an integration (auto-provisions env vars by default)\nvercel integration add neon\n\n# Open an integration's dashboard\nvercel integration open neon\n\n# Remove an integration\nvercel integration remove neon\n```\n\n#### Agent-Optimized: `discover` and `guide`\n\nAI agents can autonomously discover, install, and retrieve setup instructions for Marketplace integrations (added March 2026):\n\n```bash\n# Search the integration catalog (returns JSON for automation)\nvercel integration discover --format=json\n\n# Search with a keyword filter\nvercel integration discover database --format=json\n\n# Get agent-friendly setup guide with code snippets\nvercel integration guide neon\n\n# Full workflow: discover â†’ add â†’ guide\nvercel integration discover storage --format=json\nvercel integration add neon\nvercel integration guide neon\n```\n\n- `discover` â€” Searches the Vercel Marketplace catalog. Use `--format=json` for non-interactive output suitable for scripting and agent pipelines.\n- `guide \u003Cname>` â€” Returns getting-started documentation in agent-friendly markdown: environment variables, SDK setup, and code snippets.\n- Human-in-the-loop safety: the CLI prompts for developer confirmation when accepting Terms of Service.\n\n> Full subcommands: `discover`, `guide`, `add`, `list` (alias `ls`), `balance`, `open`, `remove`.\n\n### Project-Level Routing (No Redeploy)\n\nCreate and update routing rules â€” headers, rewrites, redirects â€” without building a new deployment. Rules take effect instantly.\n\nAvailable via dashboard (CDN tab), API, CLI, and Vercel SDK. Project-level routes run after bulk redirects and before deployment config routes.\n\n### Feature Flags\n\n```bash\n# Create a feature flag\nvercel flags add redesigned-checkout --kind boolean --description \"New checkout flow\"\n\n# List SDK keys\nvercel flags sdk-keys ls\n\n# Enable\u002Fdisable, archive, and manage flags from CLI\nvercel flags --help\n```\n\nSee `â¤³ skill: vercel-flags` for full flag configuration and adapter patterns.\n\n### Direct API Access\n\nThe `vercel api` command (added January 2026) gives direct access to the full Vercel REST API from the terminal. Designed for AI agents â€” call Vercel APIs with no additional configuration.\n\n```bash\n# Call any Vercel REST API endpoint\nvercel api GET \u002Fv9\u002Fprojects\nvercel api GET \u002Fv13\u002Fdeployments\nvercel api POST \u002Fv9\u002Fprojects\u002F:id\u002Fenv --body '{\"key\":\"MY_VAR\",\"value\":\"val\",\"target\":[\"production\"]}'\n\n# Pipe JSON output to jq\nvercel api GET \u002Fv9\u002Fprojects | jq '.[].name'\n```\n\n### Metrics\n\n```bash\n# Query project metrics (rich text output with sparklines)\nvercel metrics\n\n# Raw values for scripting\nvercel metrics --raw-values\n```\n\n## CI\u002FCD Integration\n\nRequired environment variables for CI:\n```bash\nVERCEL_TOKEN=\u003Cyour-token>\nVERCEL_ORG_ID=\u003Corg-id>\nVERCEL_PROJECT_ID=\u003Cproject-id>\n```\n\n### GitHub Actions Example\n\n```yaml\n- name: Deploy to Vercel\n  run: |\n    vercel pull --yes --environment=production --token=${{ secrets.VERCEL_TOKEN }}\n    vercel build --prod --token=${{ secrets.VERCEL_TOKEN }}\n    vercel deploy --prebuilt --prod --token=${{ secrets.VERCEL_TOKEN }}\n```\n\n## Global Options\n\n| Flag | Purpose |\n|------|---------|\n| `--token` | Authentication token (for CI) |\n| `--cwd \u003Cdir>` | Working directory |\n| `--debug` \u002F `-d` | Verbose output |\n| `--yes` \u002F `-y` | Skip confirmation prompts |\n| `--scope \u003Cteam>` | Execute as a team |\n\n## Common Workflows\n\n### First-Time Setup\n```bash\nvercel link          # Connect to Vercel project\nvercel env pull      # Get environment variables\nvercel dev           # Start local dev\n```\n\n### Deploy from CI\n```bash\nvercel pull --yes --environment=production --token=$TOKEN\nvercel build --prod --token=$TOKEN\nvercel deploy --prebuilt --prod --token=$TOKEN\n```\n\n### Quick Preview\n```bash\nvercel               # Creates preview deployment, returns URL\n```\n\n## Official Documentation\n\n- [Vercel CLI](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli)\n- [Cache Management](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fcache)\n- [MCP Integration](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\u002Fmcp)\n- [Deployments](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fdeployments)\n- [REST API](https:\u002F\u002Fvercel.com\u002Fdocs\u002Frest-api\u002Freference)\n- [GitHub: Vercel CLI](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fvercel)\n",{"name":5,"metadata":24,"description":7},{"docs":25,"sitemap":27,"priority":28,"bashPatterns":29,"pathPatterns":37,"promptSignals":43},[26],"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli","https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml",4,[30,31,32,33,34,35,36],"^\\s*vercel(?:\\s|$)","^\\s*vc(?:\\s|$)","\\bnpx\\s+vercel\\b","\\bpnpm\\s+dlx\\s+vercel\\b","\\bbunx\\s+vercel\\b","\\byarn\\s+dlx\\s+vercel\\b","\\bnpx\\s+@vercel\u002Fconfig\\b",[38,39,40,41,42],"vercel.json","vercel.ts",".vercel\u002F**",".vercelignore","now.json",{"allOf":44,"anyOf":61,"noneOf":63,"phrases":67,"minScore":82},[45,48,50,53,55,57,59],[46,47],"check","deployment",[46,49],"deploy",[51,52],"vercel","status",[51,54],"logs",[49,56],"error",[49,58],"failed",[49,60],"stuck",[47,49,51,62],"production",[64,65,66],"terraform","aws deploy","heroku",[68,69,70,71,72,73,74,75,76,77,78,79,80,81],"check deployment","check deploy","deployment status","deploy status","vercel logs","deployment logs","deploy logs","vercel inspect","is it deployed","deploy failing","deploy failed","deployment error","check vercel","vercel status",6,"main","92c2f40ebfad0c0aa3cc1faa89ffd6b23f9e8d1b","official-openai\u002Fopenai-local-vercel-vercel-cli","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill","https:\u002F\u002Fsd-skill.vercel.app","https:\u002F\u002Fgithub.com\u002Frealsudarshan","sudarshandhakal.com.np","Innvotative","2026-11-12 23:03:50",{"source":8,"skillName":5,"commands":93,"prompt":103,"zipAvailable":104},[94,97,100],{"tool":95,"command":96},"npx","npx skills add realsudarshan\u002FSD-skill --skill vercel-cli",{"tool":98,"command":99},"bunx","bunx skills add realsudarshan\u002FSD-skill --skill vercel-cli",{"tool":101,"command":102},"pnpm","pnpm dlx skills add realsudarshan\u002FSD-skill --skill vercel-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Fofficial-openai\u002Fopenai-local-vercel-vercel-cli\u002FSKILL.md",true,[106],{"path":107,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":110,"sourceHtmlUrl":111},"agents\u002Fopenai.yaml","REFERENCE","参考文档",90,"https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Fofficial-openai\u002Fopenai-local-vercel-vercel-cli\u002Fagents\u002Fopenai.yaml",[113,122,130,138,146,154],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7CW5Y6EPMPMNDWE4EN2GXRX","winui-app","Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7CW5RWFX7616ENEG573VFWG","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fvercel-deploy\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M7CW5M4VZHQPWG764X1W0S3B","security-best-practices","Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review\u002Freport, or secure-by-default coding help. Trigger only for supported languages (python, javascript\u002Ftypescript, go). Do not trigger for general code review, debugging, or non-security tasks.","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fsecurity-best-practices\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fsecurity-best-practices\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":19},"01M7CW5EBTWA7PQ54HYFT1YW39","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7CW4DA7SZ4D9JMR3P7VJVM0","openai-docs","Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains.","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":117,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":19},"01M7CW3EHY7X60KB9SYEMRD3YR","netlify-deploy","Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site\u002Frepo on Netlify, including preview and production deploys.","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fnetlify-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fnetlify-deploy\u002FSKILL.md",[],[]]