deploy-to-vercel

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

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/nimdvir/dima-publishing --skill deploy-to-vercel-nimdvir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-to-vercel
Source: https://github.com/nimdvir/dima-publishing/tree/main/.agents/skills/deploy-to-vercel
Command: npx skills add https://github.com/nimdvir/dima-publishing --skill deploy-to-vercel-nimdvir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Getting a project live on Vercel involves many branching paths depending on whether the project is git-linked, CLI-authenticated, or running in a sandboxed environment. This Skill automates that decision flow and executes the correct deployment method, always returning a live preview URL. ## 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 linking first. - Team and scope handling: Lists available Vercel teams and applies the selected team slug via --scope on all CLI commands. - No-auth fallback scripts: Ships deploy.sh and deploy-codex.sh that package a project (excluding node_modules, .git, .env), auto-detect the framework from package.json, upload to a claimable deploy endpoint, and poll until the build completes. - Use Case: You built a Next.js app in a sandboxed environment with no Vercel credentials. The Skill packages the project, deploys it via the claimable endpoint, and returns a preview URL plus a claim URL to transfer it to your Vercel account. ## Quick Start Deploy my current project to Vercel and give me the preview link.

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 [path] -y --no-wait` after authenticating with `vercel login`. If the project is linked to a git remote, committing and pushing also triggers an automatic Vercel deployment with a preview URL.

How to deploy to Vercel without authentication or login?▼

Use the claimable deploy script, which packages the project, uploads it to a deploy endpoint, and returns a preview URL plus a claim URL. Visiting the claim URL transfers the deployment to your Vercel account without prior authentication.

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

Yes, via fallback deploy scripts that require no CLI authentication. In Codex, check for the CLI first with `command -v vercel`; if unavailable or unauthenticated, run the deploy script and escalate network permissions only for the deploy command.

How does the deploy script detect my project's framework?▼

The script reads package.json and matches dependencies against an ordered list of frameworks including Next.js, Remix, Astro, SvelteKit, Nuxt, and Express. More specific frameworks are checked first, and static HTML projects are handled by renaming a single HTML file to index.html.

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

Sandboxed environments often block outbound network requests. On claude.ai, add *.vercel.com to allowed domains in capability settings; in Codex, rerun the deploy command with escalated sandbox permissions.

Should I deploy to Vercel production or preview by default?▼

Always deploy as preview unless the user explicitly requests production. Preview deployments are the default for both CLI deploys and non-production git branches; production deploys require the `--prod` flag or a push to the production branch.