What problem does it solve? Deploying to Vercel from CI pipelines, scripts, or AI agents 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 prompts. ## 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. - Deployment Workflows: Deploy previews or production builds via quick deploy (with project ID), linked projects, git push triggers, or CLI deploys, with status inspection and build logs. - Project Management: Manage environment variables, domains, team scopes, and Stripe-managed Vercel plan upgrades or downgrades. - Use Case: An AI agent in a CI environment needs to deploy a Next.js app to a Vercel team. It finds VERCEL_TOKEN in .env, exports it, links the project with vercel link --repo --scope my-team -y, and runs a preview deploy without any interactive login. ## Quick Start Deploy my project to Vercel as a preview using the token in my .env file.