Env Manager
bobmatnyc/claude-mpm
Environment variable validation, synchronization, and management across local development, CI/CD, and deployment platforms
Vercel environment variable expert guidance. An agent skill from vercel/vercel-plugin.
Install Env Vars
$ npx skills add vercel/vercel-plugin --skill env-vars -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel/vercel-plugin env-vars --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/env-vars .claude/skills/env-vars && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "env-vars" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/env-vars into .claude/skills/env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "env-vars", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vercel/vercel-plugin/tree/main/skills/env-varsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vercel/vercel-plugin --skill env-vars -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel/vercel-plugin env-vars --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/env-vars .agents/skills/env-vars && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "env-vars" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/env-vars into .agents/skills/env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "env-vars", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel/vercel-plugin --skill env-vars -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel/vercel-plugin env-vars --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/env-vars .cursor/skills/env-vars && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "env-vars" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/env-vars into .cursor/skills/env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "env-vars", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vercel/vercel-plugin.git --path skills/env-vars--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vercel/vercel-plugin --skill env-vars -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel/vercel-plugin env-vars --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/env-vars .gemini/skills/env-vars && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "env-vars" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/env-vars into .gemini/skills/env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "env-vars", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vercel/vercel-plugin env-varsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vercel/vercel-plugin --skill env-vars -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/env-vars .github/skills/env-vars && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "env-vars" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/env-vars into .github/skills/env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "env-vars", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel/vercel-plugin --skill env-vars -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel/vercel-plugin env-vars --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/env-vars .opencode/skills/env-vars && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "env-vars" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/env-vars into .opencode/skills/env-vars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "env-vars", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
env-vars- GitHub stars
- 301
- Token cost
- ~3k tokens
- SKILL.md length
- 936 words
- Files
- 2
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Vercel environment variable expert guidance. An agent skill from vercel/vercel-plugin.
- Works in 4 steps: .env (lowest priority) → .env.[environment] (development,… → .env.local (skipped in test environment) → …
- Working with .env files
- SKILL.md covers .env File Hierarchy, vercel env CLI, Bootstrap Flow (Fresh Clone /… and OIDC Token Lifecycle, plus 4 more sections
- Calls vercel, npx and npm; reaches vercel.com; needs VERCEL_OIDC_TOKEN and AI_GATEWAY_API_KEY
What it does
Env Vars is an agent skill from vercel/vercel-plugin, published by the product's own GitHub organization. Vercel environment variable expert guidance. Use when working with .env files, vercel env commands, Secret or Config variable types, OIDC tokens, or managing environment-specific configuration.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.
It sits in DevOps & Cloud, covering Secrets management and OAuth and OpenID Connect. It works with Vercel and Next.js. The repository describes itself as: Comprehensive Vercel ecosystem plugin — relational knowledge graph, skills for every major product, specialized agents, and Vercel conventions. Turns any AI agent into a Vercel…
When your agent uses it
- Working with .env files
- Vercel env commands
- Config variable types
- Managing environment-specific configuration
Example prompts
- “/env-vars”
Requirements
- Node.js
- A credential in OPENAI_API_KEY
- A credential in ANTHROPIC_API_KEY
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- .env (lowest priority)
- .env.[environment] (development, production, or test)
- .env.local (skipped in test environment)
- .env.[environment].local (highest priority, skipped in test)
What it can do on your machine
Read from SKILL.md and the folder at commit 82fa491. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
vercelnpxnpmnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
vercel.com
Also links to:
nextjs.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
VERCEL_OIDC_TOKENAI_GATEWAY_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Env Vars loads about 3k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 936 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:3
e expert guidance. Use when working with .env files, vercel env commands, Secret or Config variable types, OIDC tokens, - NoteMentions a .env fileSKILL.md:11
- '.env' - NoteMentions a .env fileSKILL.md:12
- '.env.*' - NoteMentions a .env fileSKILL.md:13
- '.env.local' - NoteMentions a .env fileSKILL.md:14
- '.env.production' - NoteMentions a .env fileSKILL.md:15
- '.env.development' - NoteMentions a .env fileSKILL.md:16
- '.env.test' - NoteMentions a .env fileSKILL.md:17
- '.env.production.local' - NoteMentions a .env fileSKILL.md:18
- '.env.development.local' - NoteMentions a .env fileSKILL.md:19
- '.env.test.local'
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 936 words (~3,029 tokens).
“You are an expert in Vercel environment variable management — .env file conventions, the vercel env CLI, OIDC token lifecycle, and environment-specific configuration.”
- name
- env-vars
- metadata.priority
- 7
- metadata.docs
- https://vercel.com/docs/environment-variables, https://vercel.com/docs/environment-variables/sensitive-environment-variables
- metadata.sitemap
- https://vercel.com/sitemap.xml
- metadata.pathPatterns
- .env, .env.*, .env.local, .env.production, .env.development, .env.test, .env.production.local, .env.development.local, .env.test.local, .env.example
- metadata.bashPatterns
- \bvercel\s+env\s+pull\b, \bvercel\s+env\s+add\b, \bvercel\s+env\s+rm\b, \bvercel\s+env\s+ls\b, \bvercel\s+env\s+update\b, \bvercel\s+env\s+run\b
- retrieval.aliases
- environment variables, env file, secrets, config vars, secret env var, sensitive env var
- retrieval.intents
- set env var, manage secrets, pull env vars, configure environment
- retrieval.entities
- .env, vercel env, OIDC, environment variable
Files
SKILL.md and 1 other file in skills/env-vars of vercel/vercel-plugin.
- SKILL.md
- .vercel.approvers
Open the folder on GitHubat commit 82fa491
Compare with similar skills
Env Vars next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Env Vars this skillvercel/vercel-plugin | 301 | — | ~3k | Automated safety check: Notes | Custom licence | |
| Env Managerbobmatnyc/claude-mpm | 155 | — | ~2k | Automated safety check: Notes | MIT | |
| Vercel Deployaiskillstore/marketplace | 430 | — | ~2.9k | Automated safety check: Notes | None | |
| Vercel Deploymentdavila7/claude-code-templates | 32k | 5 repos | ~534 | Automated safety check: Pass | MIT | |
| Clade Deploy Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Clay Deploy Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Vercel Deploy
aiskillstore/marketplace
A skill your agent uses when deploying Next.js applications to Vercel.
Vercel Deployment
davila7/claude-code-templates
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
Clade Deploy Integration
jeremylongshore/tons-of-skills-marketplace
Deploy Claude-powered applications to Vercel, Fly.io, and Cloud Run Use when working with deploy-integration patterns.
Clay Deploy Integration
jeremylongshore/tons-of-skills-marketplace
Deploy Clay-powered applications to Vercel, Cloud Run, or Docker with proper secrets management.
Azure Bicep Skill
timothywarner-org/claude-code
A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.
More from vercel/vercel-plugin
All 38 skills in this repo- Official
Deployments Cicd
vercel/vercel-plugin
Vercel deployment and CI/CD expert guidance. An agent skill from vercel/vercel-plugin.
- Official
Plugin Audit
vercel/vercel-plugin
Audit vercel-plugin performance on real-world projects. An agent skill from vercel/vercel-plugin.
- Official
Vercel CLI
vercel/vercel-plugin
Vercel CLI expert guidance. An agent skill from vercel/vercel-plugin.
- Official
AI Gateway
vercel/vercel-plugin
Vercel AI Gateway guidance for setup, model discovery, authentication, routing, fallbacks, virtual models, evaluation models, BYOK, budgets, spend reporting, observability, compatible APIs, and…
- Official
Vercel Services
vercel/vercel-plugin
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project.
- Official
Access Protected Vercel Deployment
vercel/vercel-plugin
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection.
Related
Categories
Questions about Env Vars
What does Env Vars do?
Vercel environment variable expert guidance. An agent skill from vercel/vercel-plugin. Env Vars is an agent skill from vercel/vercel-plugin, published by the product's own GitHub organization. Vercel environment variable expert guidance.
When should I use Env Vars?
Env Vars fits situations like: working with .env files; vercel env commands; config variable types; managing environment-specific configuration.
How do I install Env Vars in Claude Code?
Run `npx skills add vercel/vercel-plugin --skill env-vars -a claude-code`. Or copy the skill folder (skills/env-vars in vercel/vercel-plugin) into .claude/skills/env-vars in your project. Claude Code loads it when a task matches its description.
How do I install Env Vars in Codex?
Run `npx skills add vercel/vercel-plugin --skill env-vars -a codex`. Or copy the skill folder (skills/env-vars in vercel/vercel-plugin) into .agents/skills/env-vars in your project. Codex loads it when a task matches its description.
Can I use Env Vars in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel/vercel-plugin --skill env-vars -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/env-vars, .gemini/skills/env-vars, .github/skills/env-vars and .opencode/skills/env-vars in your project.
What does Env Vars need to run?
Going by SKILL.md and its folder, Env Vars needs the command-line tools its instructions call (vercel, npx, npm and node) and credentials named VERCEL_OIDC_TOKEN and AI_GATEWAY_API_KEY. Our summary lists: Node.js; A credential in OPENAI_API_KEY; A credential in ANTHROPIC_API_KEY.
Does Env Vars access the network?
SKILL.md names 2 domains. In commands or code: vercel.com; the agent is likely to contact it when it follows the instructions. As links in the text: nextjs.org. This is read from the text; nothing was executed.
Is Env Vars safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Env Vars use?
Env Vars has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Env Vars use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Env Vars?
Skills that share tags, products or a category with Env Vars: Env Manager (bobmatnyc/claude-mpm, 155 stars), Vercel Deploy (aiskillstore/marketplace, 430 stars), Vercel Deployment (davila7/claude-code-templates, 32k stars) and Clade Deploy Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Env Vars?
vercel (a GitHub organization, an official publisher) maintains it in vercel/vercel-plugin, which has 301 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 7, 2026.
Source: vercel/vercel-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.