What problem does it solve? Deploying to Vercel from automated or agentic environments is blocked by interactive login flows and unclear token handling. This Skill provides a complete workflow for using the Vercel CLI with access tokens, covering token discovery, project linking, deployments, environment variables, and plan management without interactive prompts. ## Core Features & Use Cases - Token-Based Authentication: Locate VERCEL_TOKEN from the environment or .env files and export it so the CLI reads it natively, avoiding insecure --token flags. - Deployment Workflows: Deploy via quick deploy with project IDs, git push triggers, or CLI deploys after linking with vercel link, defaulting to preview deployments. - Project Management: Manage environment variables, inspect deployments and build logs, configure domains, and handle Stripe Projects plan upgrades or downgrades. - Use Case: An AI agent in a CI environment needs to deploy a Next.js app to a specific Vercel team. It finds the token in .env, exports VERCEL_ORG_ID and VERCEL_PROJECT_ID, and runs vercel deploy -y --no-wait without any interactive prompts. ## Quick Start Deploy my project to Vercel as a preview using the token in my .env file and the team scope from my project URL.