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, and whether a git remote exists. This Skill automates that decision flow and executes the right deployment path, returning a live preview URL. ## 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 passes the selected team slug via --scope on all CLI commands. - No-auth fallback scripts: Ships bash scripts that package a project (excluding node_modules, .git, .env), auto-detect the framework from package.json, and deploy through a claimable endpoint returning preview and claim URLs. - Use Case: You finish a Next.js app in a sandboxed environment without Vercel credentials. The Skill packages the directory, deploys it, waits for the build, 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.