What problem does it solve? Deploying a project to Vercel involves many branching states: the project may or may not be linked, the CLI may or may not be authenticated, and the environment may be sandboxed. This Skill guides an agent through the correct deployment path for any of these situations and always returns a live URL. ## Core Features & Use Cases - State-aware deploy 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 fallback script. - Team and scope handling: Lists Vercel teams, prompts for selection when multiple exist, and passes --scope consistently across CLI commands. - No-auth fallback scripts: Ships deploy.sh and deploy-codex.sh that detect the framework from package.json, package the project excluding secrets, upload to a claimable deploy endpoint, and poll until the build completes. - Use Case: A user in a sandboxed chat environment says "deploy my app and give me the link" — the Skill packages the project, deploys it without credentials, and returns a preview URL plus a claim URL to transfer ownership. ## Quick Start Deploy my current project to Vercel as a preview and give me the live link.
