What problem does it solve? Getting a local project live on Vercel involves many decisions: whether the project is linked, whether the CLI is authenticated, which team to deploy to, and what to do in sandboxed environments without credentials. This Skill automates that decision flow and executes the right deployment path. ## Core Features & Use Cases - State-aware deployment: Detects git remotes, Vercel project linking (.vercel/project.json or .vercel/repo.json), and CLI authentication before choosing 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 it 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 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.
