env-vars

Automate Vercel environment variables and OIDC tokens across deployments.

Updated May 31, 2026

Search Tags:#deployment #vercel #environment-variables #dotenv #oidc #secret-management #env-pull

Ready to run

npx skills add https://github.com/ChristineTham/lp --skill env-vars-christinetham

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: env-vars
Source: https://github.com/ChristineTham/lp/tree/main/.agents/skills/env-vars
Command: npx skills add https://github.com/ChristineTham/lp --skill env-vars-christinetham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently manage environment variables, secrets, and OIDC tokens across local development and Vercel deployments, reducing secret leakage and configuration drift.

Core Features & Use Cases

Centralized guidance on .env hierarchies, vercel env CLI, OIDC token lifecycle, and environment scoping for production, preview, and development.
Practical workflows for pulling, setting, and validating env vars, with best practices to avoid accidental secrets exposure.

Quick Start

Pull the current environment variables into .env.local and verify required keys exist.

Frequently Asked Questions about env-vars

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I pull Vercel environment variables into my local development setup?▼

To pull Vercel environment variables locally, you can use vercel env CLI commands to fetch and download them directly into a .env.local file. This ensures your local development setup maintains consistency with your cloud deployments and avoids configuration drift.

What is the best way to manage OIDC tokens across staging and production environments?▼

Managing OIDC tokens across staging and production is best handled by applying environment scoping rules within your Vercel dashboard and CI workflows. This approach safely handles the OIDC token lifecycle and prevents accidental secret leakage across different deployment contexts.

Can I use vercel env CLI commands to set environment variables for CI workflows?▼

Yes, you can use the vercel env CLI to set and validate environment variables specifically for CI workflows. This allows you to programmatically configure environment-variable hierarchies and pull required keys without exposing secrets directly in your continuous integration pipeline.

How do .env hierarchies work when configuring local development with Vercel?▼

.env hierarchies in local development work by prioritizing specific environment files like .env.local over general ones. Using the vercel env CLI to pull variables ensures your local configuration accurately reflects the environment scoping set for your Vercel preview or production deployments.

Why does configuration drift happen with Vercel environment variables and how can I avoid it?▼

Configuration drift happens when local development, staging, and production environments use inconsistent environment variables or outdated secrets. You can avoid this drift by using the vercel env CLI to centrally pull, validate, and manage environment variables and OIDC tokens across all deployment contexts.