vercel-cli

Deploy web applications to Vercel and manage projects, domains, and environment variables via CLI.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill vercel-cli-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-cli
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/add-vercel/container-skills/vercel-cli
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill vercel-cli-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying web applications to Vercel from an agent environment requires handling authentication, non-interactive CLI flags, and post-deploy verification, which is error-prone when done manually. ## Core Features & Use Cases - Production and Preview Deployments: Run vercel deploy with --yes and --prod flags, with OneCLI proxy injecting the real auth token automatically. - Project, Domain, and Env Management: Link projects, list deployments, add domains, and push or pull environment variables non-interactively. - Pre-Send Verification: Enforces local build checks, deployment status inspection, and live URL curl checks before sharing a URL with the user. - Use Case: After finishing a Next.js feature, ask the agent to build locally, deploy to production on Vercel, verify the live URL returns HTTP 200, and report the link. ## Quick Start Deploy my project to Vercel production and confirm the live URL works before sending me the link.

Frequently Asked Questions about vercel-cli

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

FAQPage Schema
How do I deploy an app to Vercel from the command line?

Run vercel deploy --yes --prod --token placeholder from the project directory, or pass --cwd to target another path. The --yes flag skips interactive prompts and OneCLI replaces the placeholder token with the real credential.

How do I authenticate the Vercel CLI in a non-interactive environment?

Authentication is handled by OneCLI, whose HTTPS proxy injects the real Vercel token into API requests. Always pass --token placeholder on every command and verify access first with vercel whoami --token placeholder.

How do I add environment variables to a Vercel project?

Pipe the value with echo to avoid interactive prompts: echo "value" | vercel env add VAR_NAME production --token placeholder. You can also pull existing variables locally with vercel env pull --token placeholder.

Why does Vercel deploy fail with 'No framework detected'?

This error means Vercel cannot identify how to build the project. Ensure the project has a package.json with a build script, or explicitly set the framework in a vercel.json configuration file.

How do I verify a Vercel deployment is actually live?

Check the deployment status with vercel inspect <deployment-url> --token placeholder to confirm it is READY, then run curl -sI <url> and confirm the response is a 2xx or 3xx status before sharing the link.