Back to Skills

vercel-cli-with-tokens

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

25,016stars2,274forksUpdated 4/14/2026

Security Assessment

Medium Risk(50/100)

Detected risks:

Secret Exposure([SKILL.md] TOKEN=)
Sensitive File Access([SKILL.md] .env)
Security Score50/100

About vercel-cli-with-tokens

The 'vercel-cli-with-tokens' skill enables developers to deploy and manage projects on Vercel using token-based authentication, bypassing the need for interactive login via 'vercel login'. This approach is particularly useful for automated deployment pipelines, CI/CD setups, and scenarios where storing and using credentials securely is crucial. By leveraging environment variables to store access tokens, this skill ensures that sensitive credentials are not exposed in shell history or process listings, enhancing security while maintaining the flexibility of command-line project management.

Key features include the ability to locate and export a Vercel token from the environment or a '.env' file, manage project and team settings via environment variables, and deploy projects directly or through a full deploy flow. The skill provides detailed guidance for both quick deployments when project IDs are available and full deployment flows that involve linking projects. Additionally, it supports preview deployments by default, with production deployments available when explicitly requested. Users can also inspect deployment statuses to confirm successful operations.

This skill is ideal for developers, DevOps engineers, and teams using Vercel for web project hosting and seeking a streamlined, secure deployment process. It is particularly beneficial for those managing multiple projects or teams, integrating Vercel deployments into automation workflows, or maintaining strict control over token-based authentication. The skill accommodates a variety of project structures, from simple linked projects to more complex setups requiring explicit team and project IDs, making it versatile for both individual developers and larger organizations.

FAQ

How do I set up the Vercel token for CLI usage?

You can set up the token by exporting it as an environment variable named VERCEL_TOKEN. This token can be sourced from an existing environment variable, a '.env' file, or obtained directly from your Vercel account at vercel.com/account/tokens.

Do I need both VERCEL_ORG_ID and VERCEL_PROJECT_ID?

Yes, both must be set together in the environment for the CLI to correctly target a project. Setting only one of them will result in an error.

Can I pass the token directly as a command-line argument?

No. Passing the token with '--token' exposes it in shell history and process listings. Always use the environment variable VERCEL_TOKEN for secure usage.

What deployment modes are supported?

By default, deployments are made as previews. Production deployments are supported only when explicitly requested using the '--prod' flag.

Do I need to install the Vercel CLI separately?

Yes, ensure that the Vercel CLI is installed via 'npm install -g vercel' before using this skill.

Install vercel-cli-with-tokens

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill