PlugWiki

vercel-cli-with-tokens Skill for Claude Code: Use the Vercel CLI With an Access Token

Makes Claude deploy and manage Vercel projects with an access token, for setups where an interactive vercel login is not possible.

Installs
143K
on skills.sh
Stars
33.4K
on GitHub
Updated
Oct 2026
last repo commit

vercel-cli-with-tokens makes Claude use the Vercel CLI without vercel login. It first looks for a VERCEL_TOKEN in your environment, then in your .env file, and asks you if it finds none. It deploys as a preview unless you ask for production, and never passes the token as a --token flag.

Beyond deploys it covers linking projects, environment variables, deployment logs, domains and troubleshooting. It has a section on Stripe Projects plan changes and says to ask before any paid or destructive change. It bundles no files and no scripts, but it does tell Claude to run shell commands, including a global npm install of the CLI.

Good for

  • Developers or CI users who deploy with a Vercel access token
  • Teams managing env vars, domains and deployment logs from the CLI
  • Claude Code users who keep VERCEL_TOKEN in the environment or a .env file

Install vercel-cli-with-tokens

Claude Code

  1. 1

    Copy this prompt.

    Install the vercel-cli-with-tokens skill in Claude Code. Run this command:

npx skills add https://github.com/vercel-labs/agent-skills --skill vercel-cli-with-tokens

Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

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".

Sections in SKILL.md

  1. Step 1: Locate the Vercel Token
  2. A) VERCEL_TOKEN is already set in the environment
  3. B) Token is in a .env file under VERCEL_TOKEN
  4. C) Token is in a .env file under a different name
  5. D) No token found — ask the user
  6. Step 2: Locate the Project and Team
  7. CLI Setup
  8. Deploying a Project
  9. Quick Deploy (have project ID — no linking needed)
  10. Full Deploy Flow (no project ID — need to link)
  11. Deploying from a Remote Repository (code not cloned locally)
  12. About .vercel/ Directory
  13. Managing Environment Variables
  14. Inspecting Deployments
  15. Managing Domains
  16. Stripe Projects Plan Changes

Key facts

Author
Vercel (vercel-labs/agent-skills)
Installs on skills.sh
143,000 (Nov 2, 2026)
GitHub stars
33,354 (Nov 2, 2026)
skills.sh audits
Gen Agent Trust Hub: pass, Socket: pass, Snyk: warn
Last commit
2026-10-28
Files
SKILL.md only (no bundled files)
Version in SKILL.md
1.0.0
Sections
Token lookup, project and team, deploy, env vars, logs, domains, plan changes, troubleshooting

What it includes

  • Looks in the environment, then .env, then asks you

    It checks VERCEL_TOKEN, then a .env entry, then any Vercel-looking variable in .env.

    Runs code · Step 1: Locate the token

  • Uses VERCEL_PROJECT_ID and VERCEL_ORG_ID, or a project URL

    Both IDs must be set together, and then no vercel link is needed.

    Runs code · Step 2: Locate project and team

  • Preview by default, production only when you ask

    Quick deploy with a project ID, or link the project first. It asks before any git push.

    Runs code · Deploy

  • Adds, lists, pulls and removes Vercel env vars

    Pulling writes a .env.local file, and removing deletes a variable.

    Delete · Managing environment variables

  • Lists deployments, shows build logs and runtime logs

    Uses vercel ls and vercel inspect, with --logs for build logs and vercel logs for runtime request logs.

    Runs code · Inspecting deployments

  • Lists domains and adds a domain to a project

    Adding a domain changes your Vercel project.

    Runs code · Managing domains

  • Upgrade or downgrade a Vercel plan through the stripe CLI

    The skill says to ask first, because upgrades bill a real card and downgrades remove seats.

    Runs code · Stripe Projects plan changes

  • Fixes for a missing token, auth errors, wrong team and build failures

    Each has the command to run.

    Runs code · Troubleshooting

From the official docs

Permissions

High risk

This skill uses a Vercel access token that can deploy, change environment variables and add domains. Use a token scoped to one team and approve each command Claude runs.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It acts with your Vercel access token

    The skill uses the token to deploy, change env vars and add domains. Create a token scoped to a single team and delete it when you are done.

  • It searches your .env file for a token

    If VERCEL_TOKEN is not set, Claude reads .env and may look at variables with other names. Export the token yourself first so it does not need to.

  • It can pull, change and remove env vars

    vercel env pull writes a .env.local file, and vercel env rm deletes a variable. Approve these one at a time.

  • Plan changes can bill a card

    The Stripe Projects section covers paid upgrades and downgrades that remove seats. The skill says to ask first, so say no unless you mean it.

  • It installs the Vercel CLI globally

    If the CLI is missing, the skill runs a global npm install and can push to git after you approve.

Technical details
Talks tovercel.com, through the Vercel CLI
Scopes

  • Your Vercel access token (VERCEL_TOKEN)

  • Optional VERCEL_ORG_ID and VERCEL_PROJECT_ID

Questions

What does the vercel-cli-with-tokens skill do?

It makes Claude run the Vercel CLI with a token from the environment, so it can deploy, set env vars, read logs and manage domains without an interactive login.

How do I install it in Claude Code?

Use the install box above, which adds it from the vercel-labs/agent-skills repo. Then ask, for example, "deploy this project to Vercel" with VERCEL_TOKEN set.

Where do I get a Vercel token?

The SKILL.md points to vercel.com/account/tokens, where you create an access token. Give it to Claude through the VERCEL_TOKEN environment variable.

Why does it read my .env file?

When VERCEL_TOKEN is not in the environment, the skill searches .env for it, including variables with a different name that look like a Vercel token. Keep other secrets out of that file, or export the token yourself first.

How is it different from the deploy-to-vercel skill?

deploy-to-vercel picks a route, including interactive login and a no-account fallback. This one assumes you have a token and also covers env vars, logs and domains.

Does it deploy to production?

Only if you explicitly ask. The SKILL.md says to default to preview deployments.

Is it safe to install?

It handles an access token, reads your .env, and can change env vars and domains. Use a token scoped to one team, export it yourself so Claude does not have to search .env, and approve each command.

Information

updated Nov 2, 2026

Repository
vercel-labs/agent-skills
Folder
skills/vercel-cli-with-tokens

vercel-labs/agent-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4
  1. SKILL.md · github.com
  2. skills.sh listing · skills.sh
  3. GitHub repo · github.com
  4. deploy-to-vercel SKILL.md · github.com

Updated Nov 2, 2026.