What problem does it solve? Deploying to Vercel from CI pipelines or agent environments often fails because the CLI expects interactive login. This Skill provides a complete workflow for locating Vercel tokens, linking projects, deploying, and managing environment variables without interactive authentication. ## Core Features & Use Cases - Token Discovery: Locates VERCEL_TOKEN from the environment or .env files, and exports it so the CLI reads it natively instead of exposing it via --token flags. - Deployment Workflows: Covers quick deploys with project IDs, full link-and-deploy flows with or without git remotes, and preview-first deployment defaults. - Project Management: Manages environment variables, domains, deployment inspection, build logs, and Stripe Projects plan upgrades or downgrades. - Use Case: An AI agent in a CI environment needs to deploy a Next.js app to a Vercel team. It finds VERCEL_TOKEN in .env, exports it, links the project with vercel link --repo --scope team-slug -y, and runs a preview deploy. ## Quick Start Ask the agent to deploy this project to Vercel as a preview using the token stored in the environment or .env file.