What problem does it solve? Getting a local project live on Vercel involves several decisions: whether the project is linked, whether a git remote exists, and whether the Vercel CLI is authenticated. This Skill inspects the project state and picks the correct deployment path automatically, including fallback options for sandboxed environments without credentials. ## Core Features & Use Cases - State-aware deployment routing: Checks git remotes, .vercel/project.json or .vercel/repo.json linkage, and CLI authentication before choosing between git push, vercel deploy, or a no-auth script. - 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 deploy.sh and deploy-codex.sh that detect the framework from package.json, package the project excluding node_modules and .env, upload it to a claimable deploy endpoint, and poll until the build completes. - Use Case: You have a Next.js app in a sandboxed environment with no Vercel credentials. The Skill runs the fallback script, which detects Next.js, uploads a tarball, and returns a 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.
