vercel-cli-with-tokens

Deploy projects to Vercel using token-based authentication without interactive login.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/p-potvin/vaultwares-pipelines --skill vercel-cli-with-tokens-p-potvin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-cli-with-tokens
Source: https://github.com/p-potvin/vaultwares-pipelines/tree/main/.github/agents/agents/vercel-cli-with-tokens
Command: npx skills add https://github.com/p-potvin/vaultwares-pipelines --skill vercel-cli-with-tokens-p-potvin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes the need for interactive Vercel login by guiding users to deploy and manage projects using token-based authentication, reducing manual prompts and exposed secrets in command history.

Core Features & Use Cases

  • Token discovery and safe usage: Locate VERCEL_TOKEN in the environment or .env and instruct users to export it rather than passing it on the command line.
  • Project and team targeting: Explain when to use VERCEL_PROJECT_ID and VERCEL_ORG_ID, when to rely on .vercel metadata, and how to extract team slugs from project URLs.
  • Deploy flows: Provide quick deploys when project IDs are available, full link-and-deploy flows when linking is required, and guidance for git-driven or CLI-triggered deployments.
  • Environment variable management and inspection: Show non-interactive patterns for adding, listing, pulling, and removing env vars and emphasize using --format json for structured output.
  • Working agreements & safety: Default to preview deployments, ask before pushing to git, never pass tokens as CLI flags, and avoid directly modifying .vercel files.

Quick Start

Deploy the current repository as a preview to Vercel using an exported VERCEL_TOKEN and optional VERCEL_PROJECT_ID without performing an interactive login.

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 using a token without interactive login?

To deploy to Vercel without interactive login, export a valid VERCEL_TOKEN in your environment or .env file and use the CLI for preview and production deployments. This avoids manual prompts and keeps secrets out of command history.

When do I need VERCEL_PROJECT_ID and VERCEL_ORG_ID for CLI deployments?

VERCEL_PROJECT_ID and VERCEL_ORG_ID are optional but useful for quick CLI deployments when you need to target a specific project or team. If omitted, the CLI relies on existing .vercel metadata or requires a full link-and-deploy flow.

What is the safest way to pass a Vercel token to the CLI?

The safest way to pass a Vercel token is to export it as an environment variable rather than passing it as a CLI flag. This prevents exposing secrets in your command history and process lists.

Can I manage environment variables on Vercel non-interactively with the CLI?

Yes, you can manage environment variables non-interactively using the Vercel CLI to add, list, pull, and remove env vars. Using the --format json flag provides structured output for automated workflows.

Does Vercel CLI token auth work for both local and remote repository deployments?

Yes, token-based authentication works for both local and remote repository deployments. You can trigger CLI deployments directly or guide git-driven deployments using the exported VERCEL_TOKEN.

Why should I avoid directly modifying .vercel files during project linking?

You should avoid modifying .vercel files directly because they contain metadata generated by the CLI. Instead, use the project linking flow to safely associate your local repository with the correct Vercel project and team.