What problem does it solve? Deploying to Vercel from CI pipelines, scripts, or agent environments fails when vercel login requires interactive browser authentication. This Skill enables fully non-interactive Vercel CLI workflows by locating and exporting access tokens, project IDs, and team scopes from the environment or .env files. ## Core Features & Use Cases - Token Discovery & Setup: Locates VERCEL_TOKEN in the environment or .env files, exports it securely, and avoids exposing secrets via --token CLI flags. - Non-Interactive Deployments: Deploys preview or production builds using vercel deploy with project IDs, team scopes, or vercel link for git-connected projects. - Project Management: Manages environment variables, inspects deployments, views build logs, and configures domains entirely through CLI commands. - Use Case: An AI agent in a sandboxed environment needs to deploy a Next.js app to a team's Vercel project. It finds VERCEL_TOKEN in .env, exports it, links the project 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.