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".
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/vercel-labs/agent-skills /tmp/agent-skills && ln -s /tmp/agent-skills/skills/vercel-cli-with-tokens ~/.claude/skills/vercel-cli-with-tokensFrom README
Vercel CLI with Tokens Deploy and manage projects on Vercel using the CLI with token-based authentication, without relying on vercel login. Step 1: Locate the Vercel Token Before running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order: A) VERCELTOKEN is already set in the environment If this returns a value, you're ready. Skip to Step 2. B) Token is in a .env file under VERCELTOKEN If found, export it: C) Token is in a .env file under a different name Look for any variable that looks like a Vercel token (Vercel tokens typically start with vca): Inspect the output to identify which variable holds the token, then export it as VERCELTOKEN: D) No token found — ask the user If none of the above yield a token, ask the user to provide one. They can create a Vercel access token at vercel.com/account/tokens.