deploy-to-vercel

Deploy applications and websites to Vercel using CLI, git push, or claimable endpoints.

Updated May 22, 2026
One-click install
npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill deploy-to-vercel-viniciuscs84
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-to-vercel
Source: https://github.com/viniciuscs84/sdd-toolkit/tree/main/skills/deploy-to-vercel
Command: npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill deploy-to-vercel-viniciuscs84

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Deploying a project to Vercel involves many decisions: whether the project is linked, whether the CLI is authenticated, which team to target, and what to do in sandboxed environments without credentials. This Skill automates that decision flow so any project can be deployed with a preview URL returned to the user. ## Core Features & Use Cases - State-aware deployment routing: Detects git remotes, Vercel project linking (.vercel/project.json or .vercel/repo.json), and CLI authentication to choose between git push, vercel deploy, or a no-auth fallback script. - Team and scope handling: Lists available Vercel teams and passes the selected team slug via --scope on all CLI commands. - No-auth fallback scripts: Bundled shell scripts package a project (excluding node_modules, .git, .env), auto-detect the framework from package.json, upload it to a claimable deploy endpoint, and poll until the build completes. - Use Case: A user in a sandboxed AI environment says "deploy my app and give me the link" — the Skill runs the fallback script and returns a live preview URL plus a claim URL to transfer the deployment to their Vercel account. ## Quick Start Ask the assistant to deploy the current project to Vercel and return the preview URL.

Frequently Asked Questions about deploy-to-vercel

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

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

Run vercel deploy with the -y and --no-wait flags to deploy without interactive prompts and get the URL immediately. If the project is linked to Vercel with a git remote, committing and pushing also triggers an automatic deployment.

How do I deploy to Vercel without logging in?

Use the bundled deploy.sh or deploy-codex.sh script, which packages the project into a tarball and uploads it to a claimable deploy endpoint. It returns a preview URL for the live site and a claim URL to transfer the deployment to your Vercel account.

How do I deploy to a specific Vercel team?

List teams with vercel teams list --format json, then pass the chosen team slug via the --scope flag on vercel deploy, vercel link, and vercel inspect. If the project is already linked, the orgId in .vercel/project.json determines the team automatically.

Does Vercel deployment work in sandboxed environments like claude.ai or Codex?

Yes, via the no-auth fallback scripts that deploy through a claimable endpoint without credentials. In Codex, check for the CLI first with command -v vercel, and escalate network permissions only for the actual deploy command if sandboxing blocks it.

Why does my Vercel deployment fail with network errors in a sandbox?

Sandboxed environments often block outbound network calls, causing timeouts or DNS errors during deploy. On claude.ai, add *.vercel.com to allowed domains in capability settings; in Codex, rerun the deploy command with escalated permissions.

Should I deploy to Vercel production or preview by default?

Always deploy as a preview unless the user explicitly requests production. Preview deployments are the default for vercel deploy and for pushes to non-production branches; production requires the --prod flag or a push to the production branch.