Vercel Cli

This one's for anyone deploying to Vercel from the terminal instead of git push. It covers the full CLI surface: deployments, environment variables, logs, metrics, domains, and the stuff that trips people up like project linking in monorepos. The guidance is thorough on the `.vercel/project.json` versus `.vercel/repo.json` distinction, which matters more than you'd think when commands start failing. It routes you to specific references for CI automation, debugging preview deployments with `vercel curl`, and fallback patterns using `vercel api` when the CLI doesn't expose something directly. Solid if you're scripting deploys, managing multiple projects, or just prefer living in the shell.

skills.sh installs: 432
GitHub stars: 183
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add vercel/vercel-plugin --skill vercel-cli --agent claude-code

Installs into .claude/skills of the current project.

Files

Vercel CLI Skill

The Vercel CLI (vercel or vc) deploys, manages, and develops projects on the Vercel platform from the command line. Use vercel <command> --help for full flag details on any command.

The installed CLI help is the source of truth for obscure or newly added flags. If a command example here is not enough, check vercel <command> --help before acting instead of guessing.

Parse only stdout for URLs and JSON. Warnings, progress, and --help print to stderr; merge streams only when searching help text. Some help commands exit 2 after printing usage, so treat printed usage as a successful help read.

In agent/non-interactive mode, many commands report errors and required confirmations as a single JSON object on stdout with status, reason, hint, and next (runnable follow-up commands). Prefer a suggested next command over composing a retry only after confirming that it preserves the user's intended target and authorization; do not automatically run linking, authentication, or mutation follow-ups. Read commands such as list, logs, inspect, and api keep their normal output shape.