Vercel Cli
Load vercel-cli when you need to link a project, deploy previews or production, pull env vars, attach domains, or manage Marketplace integrations from the terminal with agent-safe flags.
Overview
Vercel-cli is an agent skill most often used in Ship (also Operate) that walks through Vercel CLI deploys, env vars, domains, logs, and Marketplace integrations with reference-driven commands.
Install
npx skills add https://github.com/vercel-labs/vercel-plugin --skill vercel-cliWhat is this skill?
- Five-step workflow: load skill → classify task → read `references/<topic>.md` → execute with `vercel <command> -h` → sum
- CI/agent guidance: `--yes`, `VERCEL_TOKEN` env auth, and `vercel pull` before env-dependent deploys
- Covers deploy, env vars, domains, logs, metrics, linking, local dev, databases, and Marketplace integrations
- Use `vercel curl` for preview URLs instead of disabling deployment protection
- Decision tree in SKILL.md routes user intent to the correct reference topic file
- Documented 5-step agent workflow from skill load through summarized completion
- Reference files organized under `references/<topic>.md` per CLI task type
Adoption & trust: 292 installs on skills.sh; 187 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know you need to deploy or tune Vercel but waste cycles guessing flags, env sync, and preview access patterns.
Who is it for?
Solo developers shipping Next.js or full-stack apps on Vercel who want agents to run deployments and infra tasks with consistent guardrails.
Skip if: Teams on non-Vercel hosts only, or workflows that forbid terminal deploy access and require purely dashboard-driven changes.
When should I use this skill?
When users ask to deploy a Vercel project, set environment variables, configure domains, start local dev, view logs or metrics, add databases, or manage Marketplace integrations.
What do I get? / Deliverables
After the skill runs, the agent follows the topic reference, verifies link/env prerequisites, and executes the right `vercel` commands with CI-safe auth and a concise task summary.
- Executed Vercel CLI commands with topic-appropriate flags
- Structured === Vercel CLI Task Complete === summary for the agent handoff
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
First meaningful use is shipping—getting a build onto Vercel—but the same CLI supports ongoing infra tweaks, so the canonical shelf is Ship rather than pure local Build coding. Launch subphase fits deploy-to-production, domain setup, and release-oriented `vercel` commands that unblock going live.
Where it fits
Link `.vercel/`, pull env, and deploy production after the MVP build passes local checks.
Query deployment logs and metrics or update env vars without opening every dashboard screen.
Add a Marketplace database or third-party integration while the app skeleton is still being wired.
How it compares
Use this CLI workflow skill—not generic DevOps cheat sheets that omit Vercel-specific `vercel curl`, `vercel pull`, and Marketplace integration flows.
Common Questions / FAQ
Who is vercel-cli for?
Indie builders and agent users on Claude Code or Cursor who manage Vercel projects from the terminal for deploy, env, domain, and integration tasks.
When should I use vercel-cli?
Use it in Ship when deploying or attaching domains; in Operate when pulling logs, metrics, or env updates; and whenever a plan mentions Vercel infrastructure or Marketplace integrations.
Is vercel-cli safe to install?
CLI skills can trigger real deploys and env changes—check the Security Audits panel on this page and scope `VERCEL_TOKEN` with least privilege before agent execution.
SKILL.md
READMESKILL.md - Vercel Cli
Load the Vercel CLI skill and help with project deployment and management. ## Workflow ### Step 1: Load vercel-cli skill ``` skill({ name: 'vercel-cli' }) ``` ### Step 2: Identify task type from user request Use the decision tree in SKILL.md to select the relevant reference file. ### Step 3: Read the reference file Based on task type, read `references/<topic>.md`. Use `vercel <command> -h` for full flag details. ### Step 4: Execute task **Key things to verify:** - Project is linked (`.vercel/` directory exists) - Env vars are pulled if needed (`vercel pull`) - Use `--yes` in CI/agent contexts - Use `VERCEL_TOKEN` env var for auth (not `--token`) - Use `vercel curl` to access preview deployments (don't disable protection) ### Step 5: Summarize ``` === Vercel CLI Task Complete === Topic: <topic> <brief summary of what was done> ``` <user-request> $ARGUMENTS </user-request> name: vercel-cli description: Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, managing domains, or interacting with the Vercel platform from the command line. metadata: priority: 4 docs: - "https://vercel.com/docs/cli" sitemap: "https://vercel.com/sitemap/docs.xml" pathPatterns: - 'vercel.json' - 'vercel.ts' - '.vercel/**' - '.vercelignore' - 'now.json' bashPatterns: - '^\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/config\b' promptSignals: phrases: - "check deployment" - "check deploy" - "deployment status" - "deploy status" - "vercel logs" - "vercel metrics" - "deployment logs" - "deploy logs" - "vercel inspect" - "is it deployed" - "deploy failing" - "deploy failed" - "deployment error" - "check vercel" - "vercel status" allOf: - [check, deployment] - [check, deploy] - [vercel, status] - [vercel, logs] - [vercel, metrics] - [deploy, error] - [deploy, failed] - [deploy, stuck] anyOf: - "deployment" - "deploy" - "vercel" - "production" noneOf: - "terraform" - "aws deploy" - "heroku" minScore: 6 retrieval: aliases: - vercel command line - vc cli - deploy command - vercel terminal intents: - deploy from cli - link project - manage domains - view logs from terminal entities: - vercel CLI - vercel deploy - vercel env - vercel link - vercel logs - vercel metrics chainTo: - pattern: '"functions"\s*:\s*\{|"maxDuration"\s*:|"memory"\s*:' targetSkill: vercel-functions message: 'Functions configuration detected in vercel.json — loading Vercel Functions guidance for runtime options, streaming, and Fluid Compute.' skipIfFileContains: '"crons"\s*:' - pattern: '"redirects"\s*:\s*\[|"rewrites"\s*:\s*\[|"headers"\s*:\s*\[' targetSkill: routing-middleware message: 'Routing rules in vercel.json — loading Routing Middleware guidance for platform-level request interception patterns.' # Advanced Commands ## `vercel api` — Fallback for Missing CLI Commands **Use `vercel api` when a CLI command doesn't exist for what you need.** Full access to the Vercel REST API with automatic authentication. ```bash vercel api /v2/user # GET current user vercel api /v9/projects --scope my-team # list project