What problem does it solve? Deploying to Vercel from CI pipelines, scripts, or AI agents fails when the CLI expects interactive vercel login. This Skill enables fully non-interactive Vercel CLI workflows by locating access tokens in the environment or .env files and using them securely. ## Core Features & Use Cases - Token Discovery & Secure Auth: Finds VERCEL_TOKEN in the environment or .env files (including tokens under alternate variable names) and exports it so the CLI reads it natively, never exposing secrets via --token flags. - Non-Interactive Deployments: Deploys preview or production builds using VERCEL_ORG_ID/VERCEL_PROJECT_ID, vercel link --repo, or direct CLI deploys, with git-push deploy flows that always ask before pushing. - Project Management: Manages environment variables (vercel env add/ls/pull/rm), inspects deployments and build logs, and handles domains — all scoped to the correct team. - Use Case: An AI agent in a CI environment needs to deploy a Next.js app to Vercel. It finds VERCEL_TOKEN in .env, exports it, links the repo with vercel link --repo --scope my-team -y, and deploys a preview build without any interactive prompts. ## Quick Start Deploy my project to Vercel as a preview using the token in my .env file.