vercel-cli-with-tokens

Deploy and manage Vercel projects using CLI token-based authentication.

Updated May 15, 2026
One-click install
npx skills add https://github.com/danielbere1973/promoar --skill vercel-cli-with-tokens-danielbere1973
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel-cli-with-tokens
Source: https://github.com/danielbere1973/promoar/tree/main/.agents/skills/vercel-cli-with-tokens
Command: npx skills add https://github.com/danielbere1973/promoar --skill vercel-cli-with-tokens-danielbere1973

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vercel.

What problem does it solve? Deploying to Vercel from CI pipelines, scripts, or agent environments fails when interactive vercel login is unavailable. This Skill enables full Vercel CLI workflows using access tokens from environment variables or .env files, without interactive authentication. ## Core Features & Use Cases - Token Discovery & Setup: Locates VERCEL_TOKEN from the environment or .env files, exports it securely, and avoids exposing secrets via --token flags. - Deployment Workflows: Supports quick deploys with VERCEL_PROJECT_ID/VERCEL_ORG_ID, full link-and-deploy flows with vercel link --repo, git-push deployments, and preview-by-default safety. - Project Management: Manages environment variables, domains, deployment inspection, build logs, and Stripe Projects plan changes. - Use Case: An AI agent in a headless environment needs to deploy a Next.js app to a team's Vercel project — it finds the token in .env, links the repo, deploys a preview, and returns the deployment URL. ## Quick Start Deploy this project to Vercel as a preview using the token in my .env file.

Frequently Asked Questions about vercel-cli-with-tokens

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy to Vercel without interactive login?▼

Export a Vercel access token as the VERCEL_TOKEN environment variable and the CLI reads it natively. Create tokens at vercel.com/account/tokens, then run vercel deploy with your team scope.

How do I deploy to Vercel from a CI pipeline or script?▼

Set VERCEL_TOKEN, VERCEL_ORG_ID, and VERCEL_PROJECT_ID as environment variables, then run vercel deploy -y --no-wait. The CLI skips linking and interactive prompts when these variables are present.

Should I pass the Vercel token with the --token flag?▼

No. Passing tokens via --token exposes them in shell history and process listings. Export VERCEL_TOKEN as an environment variable instead and let the CLI read it automatically.

Why does vercel deploy fail with an authentication error?▼

The token may be expired or invalid. Verify it with vercel whoami, which uses VERCEL_TOKEN from the environment. If it fails, generate a fresh token at vercel.com/account/tokens.

How do I add environment variables to a Vercel project?▼

Pipe the value into vercel env add, for example: echo "value" | vercel env add VAR_NAME production --scope <team-slug>. Use vercel env ls to list variables and vercel env pull to sync them locally.

What is the difference between vercel link and vercel link --repo?▼

vercel link --repo reads the git remote and connects to the matching Vercel project, creating .vercel/repo.json. Plain vercel link matches by directory name and creates .vercel/project.json, which is less reliable.