deploy-to-vercel Skill for Claude Code: Deploy a Project to Vercel

Makes Claude deploy your project to Vercel as a preview, choosing git push or the Vercel CLI based on how your project is set up.

Installs: 178.5K; on skills.sh
Stars: 33.4K; on GitHub
Updated: Oct 2026; last repo commit

deploy-to-vercel makes Claude deploy your project to Vercel when you ask to deploy, push it live or make a preview. It always deploys as a preview, and only does a production deploy if you ask for one. Before it does anything, it checks for a git remote, a linked Vercel project, a logged-in CLI and your teams.

It then picks a route. If the project is linked and has a git remote, it asks before committing and pushing. Otherwise it uses the Vercel CLI, and it can install the CLI and run the login for you. With no login possible, it falls back to a temporary deploy that needs no account. The skill bundles no scripts. It runs git, vercel and npx vercel@latest commands.

Good for

Developers who say "deploy my app" and want a preview link back
People who have not linked a project to Vercel yet and want Claude to set it up
Claude Code users on a machine with the Vercel CLI, or in a sandbox without a login

Install deploy-to-vercel

Claude Code

Copy this prompt.

Install the deploy-to-vercel skill in Claude Code. Run this command:

npx skills add https://github.com/vercel-labs/agent-skills --skill deploy-to-vercel

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Sections in SKILL.md

Step 1: Gather Project State
Team selection
Step 2: Choose a Deploy Method
Linked (.vercel/ exists) + has git remote → Git Push
Linked (.vercel/ exists) + no git remote → vercel deploy
Not linked + CLI is authenticated → Link first, then deploy
Not linked + CLI not authenticated → Install, auth, link, deploy
No-Auth Fallback — vercel deploy --temporary
Agent-Specific Notes
Claude Code / terminal-based agents
Sandboxed environments (claude.ai, Codex)
Output
Troubleshooting
Network Egress Error (claude.ai)
Escalated Network Access (Codex / sandboxed environments)
CLI Auth Failure

Key facts

Author: Vercel (vercel-labs/agent-skills)
Installs on skills.sh: 178,471 (Nov 2, 2026)
GitHub stars: 33,354 (Nov 2, 2026)
skills.sh audits: Gen Agent Trust Hub: pass, Socket: pass, Snyk: warn
Last commit: 2026-10-28
Files: SKILL.md only (no bundled files)
Version in SKILL.md: 4.0.0
Default: Preview deployments; production only if you ask

What it includes

Checks the git remote, .vercel link, CLI login and team list
Claude runs read-only checks first. It avoids commands that would prompt or silently link an unlinked folder.
Runs code · Step 1: Gather project state
Asks first, then commits and pushes so Vercel builds from git
This is the route the skill prefers. It never pushes without your approval, then looks up the preview URL.
Runs code · Linked with git remote: git push
Deploys with the CLI and returns the URL without waiting for the build
Claude then checks status with vercel inspect. A production deploy happens only if you ask for it.
Runs code · Linked without git: vercel deploy
Asks which team, links the project, then deploys
It prefers repo-based linking when a git remote exists, which matches your repo to existing Vercel projects.
Runs code · Not linked, CLI logged in: link then deploy
Installs the Vercel CLI globally and runs the browser login
You finish the login in your browser. If a login is not possible, the skill moves to the temporary route.
Runs code · Not linked, no CLI: install, log in, link, deploy
Deploys with no account to a temporary URL and prints a claim link
The deployment expires unless you claim it. The skill tells Claude not to share the claim link.
Runs code · No-auth fallback: vercel deploy --temporary
Lists your teams and uses the one you pick for every command
If the project is already linked, the team comes from the .vercel folder and Claude does not ask.
Runs code · Team selection

From the official docs

Permissions

High risk

This skill runs git and Vercel CLI commands that can push code and upload it to Vercel. Make sure the team and folder are right, and approve each push yourself.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It can push your commits to git
The SKILL.md runs git add, commit and push, and says to ask for approval first. Say no if you have uncommitted work you do not want swept in, because it stages everything.
It uploads your project to Vercel
A deployment uploads your project to Vercel and returns a URL. Check for secrets in the folder before you deploy, and treat the temporary claim link as private, as the SKILL.md says.
It installs software and logs in
If the Vercel CLI is missing, the skill runs a global npm install and starts a login. Approve those commands only if you want that.
It can link a folder to a Vercel project
Linking creates a .vercel folder and may create a Vercel project under the team you pick.

Technical details

Talks to	*.vercel.com. registry.npmjs.org
Scopes	Your Vercel account via the CLI login Git push access to your remote

Questions

What does deploy-to-vercel do?

It makes Claude deploy your project to Vercel and return the preview URL. It picks git push or the Vercel CLI based on whether your project is linked and has a git remote.

How do I install it in Claude Code?

Use the install box above, which adds it from the vercel-labs/agent-skills repo. Then say, for example, "deploy my app" or "create a preview deployment".

Does it deploy to production?

Not unless you ask. The SKILL.md says to always deploy as a preview. A git push to your production branch still follows your Vercel project settings, which is why Claude asks before it pushes.

Do I need a Vercel account?

Not for the fallback route. The skill can deploy to a temporary URL with no account, and the deployment expires unless you claim it. The normal routes use your Vercel login.

Does it work in Claude.ai?

The SKILL.md has a sandbox note for claude.ai and Codex. If the CLI is not logged in there, it uses the no-auth fallback. If the network is blocked, the SKILL.md tells Claude to have you add *.vercel.com and registry.npmjs.org to the allowed domains in Claude settings under Capabilities.

Is it the same as the Vercel MCP server?

The SKILL.md runs the Vercel CLI and git in your shell and does not mention the Vercel MCP server.

Is it safe to install?

It runs shell commands that can push to your git remote, install the Vercel CLI globally and upload your project to Vercel. It is told to ask before pushing. Read the SKILL.md and the permissions section on this page first.

Information

updated Nov 2, 2026

Repository: vercel-labs/agent-skills
Folder: skills/deploy-to-vercel

vercel-labs/agent-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3

SKILL.md · github.com
skills.sh listing · skills.sh
GitHub repo · github.com