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 from environment variables or .env files, without any interactive login. ## Core Features & Use Cases - Token-Based Authentication: Locate VERCEL_TOKEN in the environment or .env files and export it so the CLI reads it natively, avoiding insecure --token flags. - Flexible Deployment Flows: Deploy via quick deploy with project IDs, link projects with vercel link or vercel link --repo, or trigger git-push deployments. - Project Management: Manage environment variables, inspect deployments and build logs, and configure domains via the Vercel CLI. - Use Case: An AI agent in a sandboxed environment needs to deploy a Next.js app to a team's Vercel account. It finds VERCEL_TOKEN in .env, exports it, links the project with the team scope, and runs a preview deployment. ## Quick Start Deploy my project to Vercel as a preview using the token in my .env file.