vercel-cli-with-tokens

Vercel CLI with Tokens

Vercel CLI with Tokens is Vercel's agent skill for running the Vercel CLI with an access token instead of vercel login: deploys, environment variables, logs and domains.

Checked by CookiesForAI on : license and last change of the skill re-read from GitHub.

Written by

Install Vercel CLI with Tokens

Install this skill with the skills CLI

Terminal
npx skills add vercel-labs/agent-skills --skill vercel-cli-with-tokens

Or install every Vercel skill at once

Terminal
npx skills add vercel-labs/agent-skills

Or paste this into your coding agent: Install the agent skill vercel-cli-with-tokens from github.com/vercel-labs/agent-skills. Checked by CookiesForAI on : license and last change of the skill re-read from GitHub. A skill can include scripts that run on your computer, so read its source first.

What Vercel CLI with Tokens does

Vercel CLI with Tokens is Vercel's skill for deploying and managing Vercel projects when the CLI signs in with an access token rather than an interactive vercel login. It loads for tasks such as deploying to Vercel, setting up a project or adding environment variables. The agent looks for the token in the environment and in .env files before asking you, and points you to vercel.com/account/tokens if none is found.

Under Vercel CLI with Tokens, the agent exports the token as VERCEL_TOKEN and never passes it as a --token flag, because command-line arguments show up in shell history and process listings. With VERCEL_PROJECT_ID and VERCEL_ORG_ID set together, it deploys without linking. Otherwise it links the project, by git repository when possible. It deploys a preview unless you ask for production, and asks before any git push.

Vercel CLI with Tokens also covers setting environment variables per environment, listing and inspecting deployments, reading build and runtime logs, and adding domains. For projects managed by Stripe Projects, it lists the upgrade and downgrade commands and asks before any plan change, because upgrades bill a real card. Troubleshooting steps cover a missing or expired token, the wrong team and failed builds.

When to use Vercel CLI with Tokens

  • You want the agent to work with a Vercel access token instead of an interactive login.
  • You have a Vercel token in a .env file and want the agent to deploy with it without exposing it.
  • You want the agent to add, list or pull environment variables for a Vercel project.
  • You have a failed Vercel deployment and want the agent to read the build logs.

When to pick something else

  • You can sign in interactively and just want a preview link: use Deploy to Vercel.

Which agents Vercel CLI with Tokens works in

Vercel documents Vercel CLI with Tokens for any AI coding agent that reads Agent Skills, installed with the skills CLI. The open skills CLI also installs it into 78 agents, including Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode (we listed it with the CLI on ). See where each agent looks for skills.

We also list this company's other pages: Vercel product page and Vercel MCP server.

Vercel CLI with Tokens license

Vercel CLI with Tokens is published under MIT, stated only in the repository README (no license file). The SKILL.md has no license key, there is no LICENSE file in the skill folder or the repository, and GitHub reports no license (checked ). The only grant is the line "License: MIT" at the end of the repository README, which covers the whole collection.

More from Vercel

Lists that include vercel-cli-with-tokens