What problem does it solve? Managing environment variables across local development, preview, and production environments is error-prone: secrets get committed to git, vercel env pull silently overwrites custom variables, and local OIDC tokens expire mid-session causing confusing auth failures. This Skill provides expert guidance on the full Vercel environment variable workflow. ## Core Features & Use Cases - .env File Hierarchy: Explains the Next.js load order across .env, .env.local, and environment-specific variants, including which files are git-tracked and which hold secrets. - vercel env CLI Operations: Covers pulling, adding, listing, and removing variables with environment scoping, sensitive flags, and Git branch overrides. - OIDC Token Lifecycle: Documents how VERCEL_OIDC_TOKEN works on Vercel versus locally, and how to troubleshoot expiry and AI Gateway authentication. - Use Case: After cloning a project on a new machine, run the bootstrap sequence to link the Vercel project, pull secrets into .env.local, and verify all keys from .env.example exist. ## Quick Start Pull the Vercel environment variables for this project into .env.local and verify that every key listed in .env.example is present.