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 environment variable lifecycle. ## Core Features & Use Cases - .env File Hierarchy: Explains Next.js load order across .env, .env.local, and environment-specific variants, including which files are git-tracked and where secrets belong. - vercel env CLI Operations: Covers pulling, adding, listing, and removing variables with environment scoping, sensitive flags, and Git branch overrides. - OIDC Token Management: Documents how VERCEL_OIDC_TOKEN works on Vercel versus locally, and how to recover from token expiry. - 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 my Vercel project's environment variables into .env.local and verify that every key listed in .env.example is present.
