_pull-env-vars

Synchronize Vercel environment variables into local .env.local files.

34|6|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/flavien-ia/hypervibe-harness --skill pull-env-vars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _pull-env-vars
Source: https://github.com/flavien-ia/hypervibe-harness/tree/main/skills/_pull-env-vars
Command: npx skills add https://github.com/flavien-ia/hypervibe-harness --skill pull-env-vars

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vercel, and includes scripts (resource) components.

What problem does it solve?

This skill resolves the friction of managing environment variables across different Vercel deployment targets by providing a unified, safe interface to pull and sync configuration without manual CLI overhead.

Core Features & Use Cases

  • Environment Synchronization: Pulls variables from production, preview, or development environments directly into your local .env.local file.
  • Safe Inspection: Allows for secure verification of environment state without exposing sensitive values in chat logs.
  • Use Case: When debugging a production issue or restoring a local development environment, use this skill to quickly pull the current Vercel configuration and merge it into your local project setup.

Quick Start

Use the pull env vars skill to fetch all production environment variables and merge them into the local configuration file.

Frequently Asked Questions about _pull-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 .env file?

To pull Vercel environment variables locally, this skill retrieves configurations from your project deployments and merges them directly into your local .env.local file, automating configuration management without manual CLI overhead.

Can I sync environment variables from Vercel preview deployments to my local development environment?

Yes, you can sync environment variables from Vercel preview deployments to your local development environment. The skill fetches configurations from production, preview, or development targets and merges them into your local setup.

What do I need to set up before syncing Vercel environment variables?

Before syncing Vercel environment variables, you need the Vercel CLI installed, a Node.js runtime, and authenticated access to the target Vercel project's infrastructure. The skill relies on these dependencies to retrieve configurations.

Is it safe to inspect Vercel environment variables during local debugging?

Inspecting Vercel environment variables during local debugging is safe using this skill. It allows secure verification of your environment state without exposing sensitive configuration values in chat logs.

What is the best way to restore missing local environment variables for a Vercel project?

The best way to restore missing local environment variables for a Vercel project is using this skill to pull the current cloud configuration. It facilitates disaster recovery by synchronizing deployed settings directly into your local environment.