deploy-to-vercel

Deploy to Vercel

Deploy to Vercel is Vercel's agent skill for getting a project live: the agent checks how your project is set up, picks a deploy method and returns a preview link unless you ask for production.

Checked by CookiesForAI on : license and last change of the skill re-read from GitHub.

Written by

Install Deploy to Vercel

Install this skill with the skills CLI

Terminal
npx skills add vercel-labs/agent-skills --skill deploy-to-vercel

Or install every Vercel skill at once

Terminal
npx skills add vercel-labs/agent-skills

Or paste this into your coding agent: Install the agent skill deploy-to-vercel from github.com/vercel-labs/agent-skills. Checked by CookiesForAI on : license and last change of the skill re-read from GitHub. A skill can include scripts that run on your computer, so read its source first.

What Deploy to Vercel does

Deploy to Vercel is Vercel's skill for getting a project live from an agent session. It loads when you ask the agent to deploy your app, push it live, give you a link or create a preview deployment. It deploys as a preview unless you explicitly ask for production, and it aims to leave the project linked to Vercel so that every git push deploys.

With Deploy to Vercel, the agent first runs four checks: whether there is a git remote, whether the folder is already linked to a Vercel project, whether the Vercel CLI is installed and signed in, and which teams you belong to. If you are in several teams, it asks which one to use. An unlinked project is linked first, by repository when a remote exists. With a git remote the agent deploys by commit and push, only after you approve the push; without one it runs vercel deploy.

When the CLI cannot be installed or signed in, as in the claude.ai sandbox or Codex, a script bundled with Deploy to Vercel detects the framework from package.json, packages the project without node_modules, .git and .env files, and uploads it to a claimable deploy endpoint. You get a preview URL plus a claim URL that moves the deployment into your own Vercel account. The agent returns the link without fetching the deployed site.

When to use Deploy to Vercel

  • You built something with an agent and want a live preview link to share.
  • You have a project that is not linked to Vercel yet and want every git push to deploy it.
  • You are working in claude.ai or Codex, where the Vercel CLI cannot sign in, and still want a deployment you can claim later.
  • You want the agent to deploy a preview and leave production alone until you ask.

When to pick something else

  • You deploy from CI or a headless agent with a Vercel access token: use Vercel CLI with Tokens.
  • You want to cut cost or speed up a project already on Vercel: use Vercel Optimize.

Which agents Deploy to Vercel works in

Vercel documents Deploy to Vercel for Claude Code and other terminal agents, Claude.ai, Claude Desktop, Codex. The open skills CLI also installs it into 78 agents, including Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode (we listed it with the CLI on ). See where each agent looks for skills.

The SKILL.md has separate paths for Claude Code and other terminal agents, the claude.ai sandbox and the Codex sandbox. Its terminal fallback runs the script from ~/.claude/skills/, Claude Code's skills folder, and notes the path may differ where you installed it.

We also list this company's other pages: Vercel product page and Vercel MCP server.

Deploy to Vercel license

Deploy to Vercel is published under MIT, stated only in the repository README (no license file). The SKILL.md has no license key, there is no LICENSE file in the skill folder or the repository, and GitHub reports no license (checked ). The only grant is a License heading at the end of the repository README that says MIT, which covers the whole collection.

More from Vercel

Lists that include deploy-to-vercel