What problem does it solve? Deploying to Vercel from CI pipelines, agents, or headless environments is blocked by the interactive vercel login flow. This Skill enables full Vercel project management using access tokens sourced from environment variables or .env files, avoiding interactive prompts and unsafe token handling. ## Core Features & Use Cases - Token Discovery & Secure Auth: Locates VERCEL_TOKEN from the environment or .env files and exports it so the CLI reads it natively, never exposing secrets via --token flags. - Deployment Workflows: Supports quick deploys with VERCEL_PROJECT_ID/VERCEL_ORG_ID, repo-linked git push deploys, and CLI deploys, defaulting to preview unless production is requested. - Project Operations: 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. It finds VERCEL_TOKEN in .env, exports it, links the project with vercel link --repo --scope my-team -y, and runs vercel deploy --scope my-team -y --no-wait to produce a preview URL. ## Quick Start Deploy my project to Vercel as a preview using the token in my .env file.