deploy-to-vercel
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".
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/vercel-labs/agent-skills /tmp/agent-skills && ln -s /tmp/agent-skills/skills/deploy-to-vercel ~/.claude/skills/deploy-to-vercelFrom README
Deploy to Vercel Deploy any project to Vercel. Always deploy as preview (not production) unless the user explicitly asks for production. The goal is to get the user into the best long-term their project linked to Vercel with git-push deploys. Every method below tries to move the user closer to that state. Step 1: Gather Project State Run all four checks before deciding which method to use: Team selection If the user belongs to multiple teams, present all available team slugs as a bulleted list and ask which one to deploy to. Once the user picks a team, proceed immediately to the next step — do not ask for additional confirmation. Pass the team slug via --scope on all subsequent CLI commands (vercel deploy, vercel link, vercel inspect, etc.): If the project is already linked (.vercel/project.json or .vercel/repo.json exists), the orgId in those files determines the team — no need to ask again. If there is only one team (or just a personal account), skip the prompt and use it directly.