vercel-cli

Guides Vercel CLI usage for project linking, environment variables, deployments, and logs.

Updated May 6, 2026
One-click install
npx skills add https://github.com/UnionStreetAI/unionstreet --skill vercel-cli-unionstreetai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel-cli
Source: https://github.com/UnionStreetAI/unionstreet/tree/main/plugins/vercel/skills/vercel-cli
Command: npx skills add https://github.com/UnionStreetAI/unionstreet --skill vercel-cli-unionstreetai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing Vercel projects from the command line involves many commands for linking, environment variables, deployments, and logs, and mistakes like deploying straight to production or leaking tokens are common. This Skill provides structured guidance for operating the Vercel CLI safely and correctly. ## Core Features & Use Cases - Project & Environment Management: Link projects with vercel link, inspect and pull environment variables with vercel env ls and vercel env pull. - Deployment Workflows: Run local dev servers, create preview deployments, and inspect or stream logs from deployment URLs. - Safety Rules: Enforces reading state before mutating, preferring preview deploys before production promotes, and never printing tokens or .env* contents. - Use Case: You need to ship a feature branch. Use this Skill to link the project, pull the latest env vars, run vercel dev locally, create a preview deployment, and inspect its logs before promoting to production. ## Quick Start Use the vercel-cli skill to link my project, pull the environment variables, and create a preview deployment.

Frequently Asked Questions about vercel-cli

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

FAQPage Schema
How do I deploy a project with the Vercel CLI?▼

Run `vercel deploy` from your project directory after linking with `vercel link`. For CI pipelines, use `vercel deploy --prebuilt` with a token via `--token "$VERCEL_TOKEN"`, and prefer preview deploys before promoting to production.

How to pull Vercel environment variables locally?▼

Use `vercel env pull .env.local` after linking your project to download environment variables into a local file. List existing variables first with `vercel env ls`, and never print the contents of `.env*` files.

How do I check Vercel deployment logs from the CLI?▼

Run `vercel logs <deployment-url>` to stream logs for a specific deployment, and `vercel inspect <deployment-url>` to view its metadata. Verify your authentication first with `vercel whoami`.

Is the Vercel CLI skill a Union Street runtime provider?▼

No. This Skill is guidance only for operating the Vercel CLI and is explicitly not a Union Street sandbox or runtime plugin. It covers project operations like linking, env vars, deploys, and logs.

When should I use --token with the Vercel CLI?▼

Use `--token "$VERCEL_TOKEN"` only in non-interactive automation such as CI pipelines. For interactive sessions, authenticate with `vercel login` instead, and never print token values.