Vercel CLI with tokens
Runs the Vercel CLI from an access token instead of a browser login: finds the token, deploys previews, manages env vars, logs and domains, keeps the token out of command flags. Use when working with Vercel from a non-interactive shell.
vercel-cli-with-tokens- Author
- Vercel
- Source
- vercel-labs/agent-skills/skills/vercel-cli-with-tokens @ 1a2c79d
- License
- none stated
About this skill
What it does
The skill runs the Vercel CLI from an access token instead of vercel login, for shells with no browser. It looks for the token in order: VERCEL_TOKEN in the environment, a VERCEL_TOKEN= line in .env, another Vercel-looking variable there (tokens usually start with vca_), and only then asks you to create one at vercel.com/account/tokens. The token is exported as VERCEL_TOKEN, which the CLI reads itself, and never passed as --token, which would leave it in shell history and process listings. VERCEL_ORG_ID and VERCEL_PROJECT_ID, set together, let the CLI skip linking.
Deploys are previews unless you ask for production: vercel deploy -y --no-wait straight away with a project ID, otherwise vercel link first (--repo with a git remote), then a push (after asking) or a CLI deploy. A push from the production branch (usually main) still deploys to production. Beyond deploys: environment variables (vercel env add, ls, pull, rm), build and runtime logs, domains, and plan changes for projects managed by Stripe Projects, each confirmed with you first, since it bills a card or removes seats.
When to use it, and when not
Use it in containers, remote agents and CI-like shells, or when the agent should manage env vars, domains and logs, not only deploy.
The lookup commands printenv VERCEL_TOKEN and grep -i vercel .env print the token into the session: the skill keeps it out of command arguments, not out of the transcript. Values for vercel env add are piped in with echo "value", so they do appear in the command. The skill is a single SKILL.md.
How to run it
We do not copy this skill: it names no licence and the repository ships no licence text. Install it from Vercel's repository with the button to the source; the README's installer is npx skills add vercel-labs/agent-skills, with --skill vercel-cli-with-tokens for this one only. It needs the Vercel CLI and installs it with npm install -g vercel if missing.
- Claude Code:
/vercel-cli-with-tokens, or ask for the skill by name. - Codex:
$vercel-cli-with-tokens. - Cursor: type
/in the Agent chat and pickvercel-cli-with-tokens.
Example: /vercel-cli-with-tokens The token is in .env. Add STRIPE_SECRET_KEY to production, then deploy a preview.
How it differs from similar skills
Deploy to Vercel, Vercel Labs only deploys, through a browser login or a temporary deploy without an account; both answer to "deploy to vercel", so the agent picks by context. OpenAI's Deploy to Vercel has the same description as that one and is deploy-only too: vercel deploy -y, or an upload by its own script when there is no login. Wrangler CLI is the Cloudflare counterpart. Env and config audit moves hardcoded secrets into env vars without pushing them to a host.
Install
This skill is not copied to the catalog: the author's repository has no licence text. Install it from there.
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel