What problem does it solve? Getting a local project live on Vercel involves several 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 walks through that decision tree and executes the right deployment path, always defaulting to preview deployments unless production is explicitly requested. ## Core Features & Use Cases - State-aware deployment flow: Checks git remotes, .vercel/project.json or .vercel/repo.json linkage, and CLI authentication before choosing between git push, vercel deploy, or linking first. - 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 detect the framework from package.json, package the project excluding node_modules and .env, upload to a claimable deploy endpoint, and return preview and claim URLs. - Use Case: You have an unlinked Next.js app in a sandboxed environment with no Vercel credentials. The Skill runs the fallback script, waits for the build, and returns a live preview URL plus a claim URL to transfer the deployment to your account. ## Quick Start Deploy my current project to Vercel and give me the preview link.
