What problem does it solve? Getting a local project live on Vercel involves many decisions: whether the project is linked, whether git integration exists, whether the CLI is authenticated, and which team to deploy to. This Skill automates that decision flow and executes the right deployment path, including fallbacks 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 to choose between git push, vercel deploy, or linking first. - Team and scope handling: Lists available Vercel teams and passes the selected slug via --scope on all CLI commands. - No-auth fallback scripts: Bundled bash scripts 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: A user in a sandboxed chat environment says "deploy my app and give me the link" — the Skill detects no CLI auth, runs the fallback script, and returns a live preview URL plus a claim URL to transfer ownership. ## Quick Start Ask the assistant to deploy the current project to Vercel and return the preview link.
