vercel-cli-with-tokens
OfficialDeploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rathe…
What it does
- .vercel/project.json — from vercel link. Contains projectId and orgId.
- .vercel/repo.json — from vercel link --repo. Contains orgId, remoteName, and a projects map.
- Upgrade to Pro: stripe projects add vercel/pro (or stripe projects upgrade vercel-plan pro)
- Downgrade to Hobby: stripe projects downgrade vercel-plan hobby
- $20/month platform fee, includes $20/month of usage credit.
- Turbo build machines (30 vCPUs, 60 GB memory) by default for new projects — significantly faster builds than Hobby.
- 1 deploying seat + unlimited free Viewer seats (read-only collaborators, preview comments).
Requirements & configuration
- Deploy and manage projects on Vercel using the CLI with token-based authentication, without relying on vercel login.
- Step 1: Locate the Vercel Token
- Before running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order:
- B) Token is in a .env file under VERCELTOKEN
- C) Token is in a .env file under a different name
Configuration: VERCEL_TOKENPROJECT_URLVERCEL_ORG_IDVERCEL_PROJECT_ID
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
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".
Source
Repository: https://github.com/vercel-labs/agent-skills
vercel-cli-with-tokens FAQ
What does the vercel-cli-with-tokens skill do?
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". .vercel/project.json — from vercel link. Contains projectId and orgId. .vercel/repo.json — from vercel link --repo. Contains orgId, remoteName, and a projects map.
What does vercel-cli-with-tokens require?
Deploy and manage projects on Vercel using the CLI with token-based authentication, without relying on vercel login. Step 1: Locate the Vercel Token Before running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order: B) Token is in a .env file under VERCELTOKEN C) Token is in a .env file under a different name Configuration keys: VERCEL_TOKEN, PROJECT_URL, VERCEL_ORG_ID, VERCEL_PROJECT_ID.
How do I install vercel-cli-with-tokens?
Run: npx -y skills add https://github.com/vercel-labs/agent-skills --skill vercel-cli-with-tokens --agent claude-code — the source lives at github.com/vercel-labs/agent-skills.
Maintain vercel-cli-with-tokens?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/vercel-labs-agent-skills-vercel-cli-with-tokens?ref=badge) npx agentictools info skills/vercel-labs-agent-skills-vercel-cli-with-tokens The second line is the CLI lookup for this page — handy in READMEs and docs.