What problem does it solve? Getting a local project live on Vercel involves many branching paths: whether the project is linked, whether a git remote exists, whether the CLI is authenticated, and which team to target. This Skill automates that decision flow and handles every path, including sandboxed environments with no Vercel credentials. ## Core Features & Use Cases - State-aware deployment routing: Detects git remotes, .vercel/project.json or .vercel/repo.json linkage, 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 passes the selected 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 return preview and claim URLs. - Use Case: You finish a Next.js app in a sandboxed environment with no Vercel login. The Skill packages the directory, deploys it, waits for the build, and returns a live preview URL plus a claim URL to transfer ownership. ## Quick Start Deploy my current project to Vercel and give me the preview link.
