vercel-cli-with-tokens

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/MohamadJoumaa/Direct --skill vercel-cli-with-tokens-mohamadjoumaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-cli-with-tokens
Source: https://github.com/MohamadJoumaa/Direct/tree/main/.cursor/skills/vercel-cli-with-tokens
Command: npx skills add https://github.com/MohamadJoumaa/Direct --skill vercel-cli-with-tokens-mohamadjoumaa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vercel.

What problem does it solve? Deploying to Vercel from CI pipelines, scripts, or agent environments fails when the CLI expects interactive vercel login. This Skill provides a complete workflow for authenticating with access tokens, locating project and team identifiers, and running deployments without any interactive prompts. ## Core Features & Use Cases - Token Discovery and Setup: Locates VERCEL_TOKEN from the environment or .env files, exports it safely, and avoids exposing secrets via --token flags. - Deployment Workflows: Covers quick deploys with VERCEL_PROJECT_ID, full link-and-deploy flows with vercel link --repo, git-push deployments, and preview-by-default behavior. - Project Management: Manages environment variables, domains, deployment inspection, build logs, and Stripe Projects plan changes. - Use Case: An AI agent in a sandboxed environment needs to deploy a Next.js app to a client's Vercel team. It finds the token in .env, links the repo with vercel link --repo --scope team-slug -y, deploys a preview, and returns the URL. ## Quick Start Deploy my 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 a token at vercel.com/account/tokens, then run vercel deploy with your team scope. Never pass the token via the --token flag, which exposes it in shell history.

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 -y flag skips confirmation prompts and the IDs let the CLI target the project without a .vercel directory or vercel link step.

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. The --repo variant is more reliable when a git remote exists.

Why does Vercel CLI authentication fail with a token?

Authentication failures usually mean the token is expired, invalid, or not exported in the current shell. Verify with vercel whoami, which reads VERCEL_TOKEN from the environment, and check that the variable is set with printenv VERCEL_TOKEN.

How do I add environment variables to a Vercel project from the CLI?

Pipe the value into vercel env add, for example: echo "value" | vercel env add VAR_NAME production --scope team-slug. List variables with vercel env ls, pull them locally with vercel env pull, and remove them with vercel env rm.