env-vars

Manage Vercel environment variables across development, preview, and production environments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you manage Vercel environment variables without leaking secrets, confusing local overrides, or breaking deployments with stale configuration.

Core Features & Use Cases

  • Environment File Guidance: Explains how env files load in Next.js and which values belong in each environment-specific file.
  • Vercel CLI Workflow: Supports pulling, adding, listing, and removing variables with the right environment scope.
  • Secure Authentication: Covers OIDC token behavior so local development and deployed apps can access Vercel services safely.
  • Use Case: A developer can use this Skill to set up a new project, verify required keys, and recover quickly when a local token expires.

Quick Start

Ask the assistant to audit your Vercel environment setup, identify missing variables, and tell you exactly where each secret or public setting should be stored.

Frequently Asked Questions about env-vars

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

FAQPage Schema
How do I pull and sync Vercel environment variables for local Next.js development?

Vercel environment variables are managed by pulling scoped secrets into local dotenv files via the Vercel CLI. This Skill guides correct env file hierarchy for development, preview, and production scopes without leaking secrets.

What is the correct Next.js env file hierarchy for storing secrets and public variables?

Next.js env file hierarchy dictates which values belong in environment-specific files to prevent local override conflicts. This Skill audits your dotenv structure and maps each secret or public setting to its correct scope.

Can I use Vercel CLI to add and remove environment variables across different deployment scopes?

Yes, the Vercel CLI supports adding, listing, and removing environment variables with specific environment scopes. This Skill applies scoped secrets correctly across development, preview, and production deployments.

Why does my local Vercel CLI authentication token expire and how do I refresh it?

Local Vercel CLI authentication tokens expire due to OIDC token behavior governing secure service access. This Skill explains OIDC refreshable authentication so local development and deployed apps recover quickly when tokens expire.

What's the best way to audit Vercel secrets and identify missing environment variables?

The best way to audit Vercel secrets is to review the environment setup and identify missing variables. This Skill verifies required keys and maps each secret or public setting to its correct env file location.

Does managing Vercel environment variables work without breaking deployments with stale configuration?

Managing Vercel environment variables safely prevents breaking deployments caused by stale configuration. This Skill ensures safe secret handling, correct environment scoping, and proper env file hierarchy across development, preview, and production environments.