Manages Vercel environment variables, .env files, and OIDC token lifecycle.
npx skills add https://github.com/AarnavBaddam/skills --skill env-vars-aarnavbaddam
Please help me install this Agent Skill. Skill: env-vars Source: https://github.com/AarnavBaddam/skills/tree/main/env-vars Command: npx skills add https://github.com/AarnavBaddam/skills --skill env-vars-aarnavbaddam
vercel env pull silently overwrites custom variables, local OIDC tokens expire mid-session, and standalone scripts fail because they don't auto-load .env.local. This Skill provides expert guidance to avoid these pitfalls. ## Core Features & Use Cases - .env File Hierarchy Guidance: Explains Next.js load order, which files are git-tracked, and where secrets belong. - vercel env CLI Workflows: Covers pull, add, ls, and rm commands, including bootstrap flows for fresh clones and re-pulling after secret changes. - OIDC Token Lifecycle: Explains how VERCEL_OIDC_TOKEN works on Vercel versus locally, and how to troubleshoot expiry and auth errors. - Use Case: You clone a project on a new machine and need it running fast. Follow the bootstrap sequence: vercel link, vercel env pull .env.local --yes, then verify all keys from .env.example exist. ## Quick Start Ask the assistant to pull the Vercel environment variables for your project into .env.local and verify that every key listed in .env.example is present.High-intent search queries and answers about installing and using this skill.
Run `vercel env pull .env.local` after linking your project with `vercel link`. Add `--environment=production` or `--environment=preview` to target a specific environment, and `--yes` to overwrite without prompting.
Next.js loads `.env` first, then `.env.[environment]`, then `.env.local` (skipped in test), and finally `.env.[environment].local` with highest priority. Later files override earlier ones.
The `vercel env pull` command replaces the entire target file, removing any manually added variables. Keep custom variables in `.env.development.local`, which Next.js loads after `.env.local`, or back them up before pulling.
The local `VERCEL_OIDC_TOKEN` provisioned by `vercel env pull` expires after roughly 12 hours. Re-run `vercel env pull .env.local --yes` to get a fresh token, ideally at the start of each dev session.
Only Next.js auto-loads `.env.local`; standalone scripts like drizzle-kit or tsx need explicit loading. Use dotenv-cli (`npx dotenv -e .env.local -- npx tsx script.ts`) or source the file manually before running.
No. Variables prefixed with `NEXT_PUBLIC_` are bundled into the browser and publicly visible, so never put secrets in them. Keep secrets in server-only variables set via the Vercel Dashboard or `vercel env add`.
javi2481Deploys and manages projects with credential-free token authentication.
gil00pitaDeploy Next.js applications to Vercel production and preview environments.
dennisonbertramScans .env files and code for exposed secrets and missing entries.
openaiManages Vercel environment variables via .env files, vercel env CLI, and OIDC tokens.