Localized reading guide
deploy-to-vercelPurpose, usage and source
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".
Source retrieved:
- Source repository
- vercel-labs/agent-skills
- SKILL.md
skills/deploy-to-vercel/SKILL.md- Repository stars
- 33,269
- Repository updated
- 2026-10-29
- Categories
- Automation
- Last collected
License: Unspecified
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
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".
How the upstream workflow works
Step 1: Gather Project State
Run all four checks before deciding which method to use:
Upstream passage · L15 ↗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 setup: their project linked to Vercel with git-push deploys. Every method below tries to move the user closer to that state.
Upstream passage · L9 ↗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.):
# 1. Check for a git remote
git remote get-url origin 2>/dev/null
# 2. Check if locally linked to a Vercel project (either file means linked)
cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null
# 3. Check if the Vercel CLI is installed and authenticated
vercel whoami 2>/dev/null
# 4. List available teams (if authenticated)
vercel teams list --format json 2>/dev/nullRequirements and setup
Sandboxed environments (claude.ai, Codex)
Check whether the CLI is logged in with vercel whoami. If it is, follow Step 2, including team selection. If it isn't, use the no-auth fallback.
Escalated Network Access (Codex / sandboxed environments)
If deployment fails due to network issues (timeouts, DNS errors, connection resets) in a sandboxed environment, rerun with escalated permissions (sandbox_permissions=require_escalated). Do not escalate the initial CLI availability check — only escalate the actual deploy command. Example guidance to the user:
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Deploy to Vercel
- Step 1: Gather Project State
- Team selection
- 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 - Claude Code / terminal-based agents
- Sandboxed environments (claude.ai, Codex)
- Output
- Network Egress Error (claude.ai)
- Escalated Network Access (Codex / sandboxed environments)
- CLI Auth Failure
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
1a2c79d4e6c4a2283dc2c614b6538cbe1ed5ca62- Source SHA-256
418ca2a60d35c551e6cb645f4e82c1b704a8335486ffe74b1b3d0617a17504e5