What problem does it solve? Getting a local project live on the internet involves many decisions: checking git remotes, verifying CLI authentication, linking projects to teams, and choosing between git-push and direct CLI deploys. This Skill automates that decision flow and handles fallback paths for sandboxed environments where authentication is not possible. ## Core Features & Use Cases - State-aware deployment: Inspects git remotes, .vercel/ link files, and CLI authentication to pick the right deploy method (git push, vercel deploy, or link-then-deploy). - Team and scope handling: Lists available Vercel teams and applies the correct --scope flag across all CLI commands. - No-auth fallback scripts: Ships deploy.sh and deploy-codex.sh that package a project, 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, which detects Next.js, packages the project excluding node_modules and .env, 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.