deploy-to-vercel

Deploy projects to Vercel via CLI, git push, or claimable no-auth endpoints.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Ramadan-Elgamal/Autobees --skill deploy-to-vercel-ramadan-elgamal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-to-vercel
Source: https://github.com/Ramadan-Elgamal/Autobees/tree/main/.agents/skills/deploy-to-vercel
Command: npx skills add https://github.com/Ramadan-Elgamal/Autobees --skill deploy-to-vercel-ramadan-elgamal

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 without credentials. This Skill automates that decision flow and always returns a working deployment URL. ## Core Features & Use Cases - State-aware deploy routing: Detects git remotes, Vercel project linking (.vercel/project.json or .vercel/repo.json), and CLI auth status to pick the right deploy method. - Multiple deploy methods: Git push for linked repos, vercel deploy for linked projects without git, link-then-deploy for new projects, and no-auth fallback scripts for sandboxed environments like claude.ai and Codex. - Framework auto-detection: Bundled shell scripts detect over 40 frameworks (Next.js, Astro, Remix, SvelteKit, and more) from package.json and package projects excluding node_modules and .env files. - Use Case: You finish a Next.js app in a sandboxed environment with no Vercel credentials. The Skill packages the project, uploads it via the claimable deploy endpoint, and returns a preview URL plus a claim URL to transfer ownership. ## 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 with the -y and --no-wait flags after linking your project with vercel link. If the project has a git remote and is linked, committing and pushing triggers an automatic deployment instead.

How do I deploy to Vercel without logging in?▼

Use the bundled deploy.sh or deploy-codex.sh fallback scripts, which package your project and upload it to a claimable deploy endpoint. They return 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 claude.ai or Codex?▼

Yes, via no-auth fallback scripts that require no Vercel credentials. On claude.ai you may need to allowlist *.vercel.com in network settings; in Codex, the deploy command may need escalated network permissions.

How do I deploy to a specific Vercel team?▼

List teams with vercel teams list --format json, then pass the chosen team slug via --scope on vercel link and vercel deploy commands. Already-linked projects use the orgId stored in .vercel/project.json or .vercel/repo.json.

Why does vercel link prompt interactively or fail to match my project?▼

Plain vercel link matches by directory name, which often fails when local and Vercel project names differ. Use vercel link --repo when a git remote exists, since it matches projects by the repository URL instead.

Should I deploy to preview or production on Vercel?▼

Always deploy as preview unless production is explicitly requested. Preview deploys use vercel deploy without --prod, while production deploys require the --prod flag and should only run on explicit user instruction.