What problem does it solve? Deploying to Vercel from CI pipelines, scripts, or agent environments fails when the CLI expects interactive vercel login. This Skill provides a complete workflow for authenticating with access tokens, locating project and team identifiers, and running deployments without any interactive prompts. ## Core Features & Use Cases - Token Discovery and Setup: Locates VERCEL_TOKEN from the environment or .env files, exports it safely, and avoids exposing secrets via --token flags. - Deployment Workflows: Covers quick deploys with VERCEL_PROJECT_ID, full link-and-deploy flows with vercel link --repo, git-push deployments, and preview-by-default behavior. - Project Management: Manages environment variables, domains, deployment inspection, build logs, and Stripe Projects plan changes. - Use Case: An AI agent in a sandboxed environment needs to deploy a Next.js app to a client's Vercel team. It finds the token in .env, links the repo with vercel link --repo --scope team-slug -y, deploys a preview, and returns the URL. ## Quick Start Deploy my project to Vercel as a preview using the token in my .env file.