vercel-cli
/vercel-cli
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.
- Author
- 420company ↗
- Repository
- artemis ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 38
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Critical: Project Linking
- Quick Start
- Decision Tree
- Anti-Patterns
SKILL.md preview
---
name: vercel-cli
description: 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.
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"
- "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]
- [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
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.'
---
# 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> -h` for full flag details on any command.
## Critical: Project Linking
Commands must be run from the directory containing the `.vercel` folder (or a subdirectory of it). How `.vercel` gets set up depends on your project structure:
- **`.vercel/project.json`**: Created by `vercel link`. Links a single project. Fine for single-project repos, and can work in monorepos if there's only one project.
- **`.vercel/repo.json`**: Created by `vercel link --repo`. Links a repo that may contain multiple projects. Always a good idea when any project has a non-root directory (e.g., `apps/web`).
Running from a project subdirectory (e.g., `apps/web/`) skips the "which project?" prompt since it's unambiguous.
**When something goes wrong, check how things are linked first** — look at what's in `.vercel/` and whether it's `project.json` or `repo.json`. Also verify you're on the right team with `vercel whoami` — linking while on the wrong team is a common mistake.
## Quick Start
```bash
npm i -g vercel
vercel login
vercel link # single project
# OR
vercel link --repo # monorepo
vercel pull
vercel dev # local development
vercel deploy # preview deployment
vercel --prod # production deployment
```
## Decision Tree
Use this to route to the correct reference file:
- **Deploy** → `references/deployment.md`
- **Local development** → `references/local-development.md`
- **Environment variables** → `references/environment-variables.md`
- **CI/CD automation** → `references/ci-automation.md`
- **Domains or DNS** → `references/domains-and-dns.md`
- **Projects or teams** → `references/projects-and-teams.md`
- **Logs, debugging, or accessing preview deploys** → `references/monitoring-and-debugging.md`
- **Blob storage** → `references/storage.md`
- **Integrations (databases, storage, etc.)** → `references/integrations.md`
- **Access a preview deployment** → use `vercel curl` (see `references/monitoring-and-debugging.md`)
- **CLI doesn't have a command for it** → use `vercel api` as a fallback (see `references/advanced.md`)
- **Node.js backends (Express, Hono, etc.)** → `references/node-backends.md`
- **Monorepos (Turborepo, Nx, workspaces)** → `references/monorepos.md`
- **Bun runtime** → `references/bun.md`
- **Feature flags** → `references/flags.md`
- **Advanced (API, webhooks)** → `references/advanced.md`
- **Global flags** → `references/global-options.md`
- **First-time setup** → `references/getting-started.md`
## Anti-Patterns
- **Wrong link type in monorepos with multiple projects**: `vercel link` creates `project.json`, which only tracks one project. Use `vercel link --repo` instead. When things break, check `.vercel/` first.
- **Letting commands auto-link in monorepos**: Many commands implicitly run `vercel link` if `.vercel/` doesn't exist. This creates `project.json`, which may be wrong. Run `vercel link` (or `--repo`) explicitly first.
- **Linking while on the wrong team**: Use `vercel whoami` to check, `vercel teams switch` to change.
- **Forgetting `--yes` in CI**: Required to skip interactive prompts.
- **Using `vercel deploy` after `vercel build` without `--prebuilt`**: The build output is ignored.
- **Hardcoding tokens in flags**: Use `VERCEL_TOKEN` env var instead of `--token`.
- **Disabling deployment protection**: Use `vercel curl` instead to access preview deploys.
Files in this package (38)
- SKILL.json 1 KB
- SKILL.md 6 KB
- overlay.yaml 2 KB
- command/vercel.md 1 KB
- references/advanced.md 1 KB
- references/bun.md 1 KB
- references/ci-automation.md 2 KB
- references/deployment.md 2 KB
- references/domains-and-dns.md 1 KB
- references/environment-variables.md 1 KB
- references/flags.md 3 KB
- references/getting-started.md 1 KB
- references/global-options.md 1 KB
- references/integrations.md 7 KB
- references/local-development.md 1 KB
- references/monitoring-and-debugging.md 1 KB
- references/monorepos.md 3 KB
- references/node-backends.md 3 KB
- references/projects-and-teams.md 1 KB
- references/storage.md 1 KB
- upstream/SKILL.md 4 KB
- upstream/command/vercel.md 1 KB
- upstream/references/advanced.md 1 KB
- upstream/references/bun.md 1 KB
- upstream/references/ci-automation.md 2 KB
- upstream/references/deployment.md 2 KB
- upstream/references/domains-and-dns.md 1 KB
- upstream/references/environment-variables.md 1 KB
- upstream/references/flags.md 3 KB
- upstream/references/getting-started.md 1 KB
- upstream/references/global-options.md 1 KB
- upstream/references/integrations.md 7 KB
- upstream/references/local-development.md 1 KB
- upstream/references/monitoring-and-debugging.md 1 KB
- upstream/references/monorepos.md 3 KB
- upstream/references/node-backends.md 3 KB
- upstream/references/projects-and-teams.md 1 KB
- upstream/references/storage.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · 420company/artemis | 95 | MIT |
| vercel-labs/vercel-plugin | 100 | Apache-2.0 |
| vercel/vercel | 100 | Apache-2.0 |
| vercel/vercel-plugin | 100 | Apache-2.0 |
| nanocoai/nanoclaw | 100 | MIT |
| mcarmona1064-cell/clawbridge-ai | 100 | MIT |
| mcarmona1064-cell/clawbridge-ai | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 7e85d1cf9f36 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100local-vercel-cli-806d4680
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. - 100managing-vercel
Vercel platform CLI for frontend deployments, serverless functions, and edge network management. Use for deploying applications, managing domains, environment variables, and debugging deployments. - 100local-vercel-api-21362b29
Vercel app and REST API expert guidance. Use when the agent needs live access to Vercel projects, deployments, environment variables, domains, logs, or documentation through the connected Vercel app or REST API. - 100vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. \"deploy to vercel\", \"set up vercel\", \"add environment variables to vercel\". - 100vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. \"deploy to vercel\", \"set up vercel\", \"add environment variables to vercel\". - 100vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".