deploy-to-vercel

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

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill deploy-to-vercel-ferrarifankid04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-to-vercel
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/claude-code/skills/deploy-to-vercel
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill deploy-to-vercel-ferrarifankid04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Getting a local project live on Vercel involves many branching paths: checking git remotes, verifying CLI authentication, linking projects to teams, and handling sandboxed environments where login is impossible. 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 deploy routing: Detects git remotes, Vercel project linkage (.vercel/project.json or repo.json), and CLI auth status, then picks the right method: git push, vercel deploy, or link-then-deploy. - 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 bash scripts that package a project (auto-detecting 40+ frameworks from package.json), upload it to a claimable deploy endpoint, and return preview and claim URLs without any Vercel login. - Use Case: A user in a sandboxed AI environment says "deploy my app and give me the link" — the Skill detects no CLI auth, runs the fallback script, and returns a live preview URL plus a claim URL to transfer ownership. ## Quick Start Ask the agent to deploy the current project to Vercel and return 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 with the -y and --no-wait flags to get an immediate deployment URL without blocking on the build. If the project is not linked yet, run vercel link first, then deploy. Use vercel inspect on the returned URL to check build status.

How do I deploy to Vercel without logging in?

Use the claimable deploy script included with this Skill, which packages your project, auto-detects the framework from package.json, and uploads it to a deploy endpoint. It returns a preview URL for the live site and a claim URL to transfer the deployment to your Vercel account.

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

Yes, via fallback scripts that require no authentication. The Codex variant posts to a Codex deploy endpoint and the claude.ai variant uses a separate endpoint; both return preview and claim URLs. Network restrictions may require escalating permissions or allowlisting vercel.com domains.

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 commands. If the project is already linked, the orgId in .vercel/project.json determines the team automatically.

Why does vercel link fail or prompt unexpectedly?

In an unlinked directory, commands like vercel link or vercel ls trigger interactive prompts or silently link as a side effect. Only vercel whoami is safe for state checks; detect linkage by reading .vercel/project.json or .vercel/repo.json instead.

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 vercel deploy and for pushes to non-production branches; production requires the --prod flag or a push to the production branch.