vercel-cli-with-tokens

npx skills add sickn33/agentic-awesome-skills --skill vercel-cli-with-tokens --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Vercel CLI with Tokens Deploy and manage projects on Vercel using the CLI with token-based authentication, without relying on `vercel login`. ## When to Use - Use this skill when the task matches this description: 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". ## 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) `VERCEL_TOKEN` is already set in the environment ```bash [ -n "${VERCEL_TOKEN:-}" ] && printf 'VERCEL_TOKEN is set\n' ``` If this reports a configured token, you're ready. Skip to Step 2. ### B) Token is in a `.env` file under `VERCEL_TOKEN` ```bash grep -q '^VERCEL_TOKEN=' .env 2>/dev/null && printf 'VERCEL_TOKEN is present in .env\n' ``` If found, export it: ```bash VERCEL_TOKEN="$(sed -n 's/^VERCEL_TOKEN=//p' .env | tail -n 1)" export VERCEL_TOKEN ``` ### C) Token is in a `.env` file under a different name Look for any variable that looks like a Vercel token (Vercel tokens ty

grep -q '^VERCEL_TOKEN=' .env 2>/dev/null && printf 'VERCEL_TOKEN is present in .env\n'
export VERCEL_TOKEN
grep -Eio '^[A-Z0-9_]*VERCEL[A-Z0-9_]*(?==)' .env 2>/dev/null
Bad — token visible in shell history and process listings
vercel deploy --token "vca_abc123"
Good — CLI reads VERCEL_TOKEN from the environment
vercel deploy
Check environment
Or check .env
e.g. "my-team" from "https://vercel.com/my-team/my-project"