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.

DevOpsPack: Vercel skillslinkvercel-cli-with-tokens
Author
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 pick vercel-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.

Open the source

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.

More from the pack Vercel skills

React and Next.js performance rules

Gives the agent Vercel's 70 React and Next.js performance rules, ranked by impact: request waterfalls, bundle size, server work, re-renders, rendering. Use when writing, refactoring or reviewing React or Next.js code for speed.

React composition patterns

Applies eight Vercel rules that replace boolean props with compound components, provider-held state and explicit variants, plus React 19 ref and use() changes. Use when a component has too many flags or when designing a component library.

React Native best practices

Applies Vercel's React Native and Expo rules: virtualized lists, transform and opacity animations, native navigators, expo-image, state, monorepo setup. Use when building or speeding up a mobile app or reviewing React Native code.

React view transitions

Implements animations with React's View Transition API: shared element morphs, Suspense reveals, list reorder and directional route slides, with CSS recipes and Next.js integration. Use when adding page or state transitions to a React or Next.js app.

Deploy to Vercel, Vercel Labs

Deploys a project to Vercel as a preview, choosing git push, CLI deploy, linking first or a temporary deploy without an account by the project's state, and returns the URL. Use when asked to deploy an app and get a link.

Vercel cost and performance tuning

Audits a deployed Vercel project for cost and performance: collects metrics first, picks candidates by fixed thresholds, inspects only flagged routes and returns verified, cited recommendations. Use when cutting a Vercel bill or fixing slow routes.

Web Interface Guidelines review

Reviews UI code against Vercel's Web Interface Guidelines, fetched fresh on each run, and lists findings as file:line: accessibility, focus, forms, animation, typography, images, performance. Use when checking components or pages before a pull request.

Writing Guidelines review

Reviews docs and prose against Vercel's writing handbook, fetched fresh on each run, and lists findings as file:line: voice, structure, headings, code samples, units, typography. Use when checking English docs before publishing.