What problem does it solve? Deploying a project to Vercel involves many possible states — linked or unlinked projects, authenticated or missing CLI credentials, git remotes or none — and choosing the wrong path leads to failed or interactive-blocking commands. This Skill inspects the project state and picks the correct deployment method automatically. ## 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 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 deploy.sh and deploy-codex.sh that package a project (excluding node_modules, .git, .env), auto-detect the framework from package.json, upload to a claimable deploy endpoint, and return preview and claim URLs. - Use Case: You have 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.
