env-vars

Manage Vercel environment variables and OIDC tokens via the vercel CLI.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Moisesjr20/gueclaw --skill env-vars-moisesjr20
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-vars
Source: https://github.com/Moisesjr20/gueclaw/tree/main/.agents/skills/env-vars
Command: npx skills add https://github.com/Moisesjr20/gueclaw --skill env-vars-moisesjr20

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides clear, practical guidance to securely manage Vercel environment variables and OIDC tokens, preventing leaked secrets, misconfigured environments, and authentication failures during local development and deployments.

Core Features & Use Cases

  • Environment bootstrapping: Steps to pull project secrets into .env.local and verify required keys against .env.example.
  • CLI operations & lifecycle: Practical usage patterns for vercel env pull/add/ls/rm and strategies to avoid overwriting custom local variables.
  • OIDC and troubleshooting: How OIDC tokens are injected, refresh behaviour, common failure modes, and remediation steps for local development.
  • Use case: On a fresh developer machine, follow the bootstrap flow to link the project, pull secrets into .env.local, and validate that NEXT_PUBLIC variables are safe for client exposure.

Quick Start

Run vercel link then vercel env pull .env.local --yes and confirm required keys from .env.example are present.

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 a local .env file?

Pull Vercel environment variables by linking the project with vercel link, then running vercel env pull .env.local --yes to download secrets and verify required keys against .env.example.

How does the Vercel CLI handle adding and removing environment variables?

The Vercel CLI manages environment variables through vercel env add, ls, and rm commands, allowing you to update deployment configurations while applying strategies to avoid overwriting custom local variables.

Why are my NEXT_PUBLIC environment variables not updating in Next.js?

NEXT_PUBLIC environment variables must be protected and correctly exposed for client-side rendering; troubleshooting involves verifying their presence in .env.local and ensuring they are safely injected during the build process.

What is the best way to troubleshoot OIDC token refresh failures during local development?

Troubleshoot OIDC token refresh failures by examining how tokens are injected, checking the refresh behavior, and applying remediation steps to resolve authentication flow issues in your local development environment.

Does this approach work for bootstrapping a fresh developer machine with Next.js and Vercel?

Yes, the bootstrap flow links the project, pulls secrets into .env.local, and validates NEXT_PUBLIC variables, making it suitable for setting up a fresh developer machine for Next.js and Vercel projects.

What is the correct .env file hierarchy and precedence for Next.js projects?

The .env file hierarchy determines variable precedence, with .env.local overriding defaults for local development, ensuring required keys are present and correctly prioritized for secure Vercel deployments.