What problem does it solve? Managing environment variables across Vercel deployments and local development 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 Guidance: Explains the Next.js load order (.env, .env.[environment], .env.local) and which files are safe to commit versus gitignored. - 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 deployments versus locally, and how to troubleshoot expiry after ~12 hours. - Use Case: After cloning a project on a new machine, run vercel link followed by vercel env pull .env.local --yes, then verify all keys from .env.example exist before starting development. ## Quick Start Pull the Vercel environment variables for this project into .env.local and verify that every key listed in .env.example is present.