How do I install the Vercel Env Vars skill?

Run npx skillmds@latest add different-ai/vercel-env-vars in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vercel Env Vars safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vercel Env Vars?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vercel Env Vars free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vercel Env Vars?

different-ai (@different-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vercel Env Vars by different-ai — Agent Skill

Name: Vercel Env Vars
Author: different-ai

Vercel Env Vars

Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"

different-ai 8df58c3 3 files · 2.8 KB Updated Sep 17, 2026

File contents

Quick Usage (Already Configured)

1) Check Vercel access

npx vercel whoami
npx vercel teams ls

2) Link the local app directory to the target project

npx vercel link --yes --scope prologe --project openwork-landing

3) Add an env var to production

npx vercel env add MY_ENV_VAR production --scope prologe --value "value" --yes

4) Add the same env var to preview and development

npx vercel env add MY_ENV_VAR preview "" --scope prologe --value "value" --yes
npx vercel env add MY_ENV_VAR development --scope prologe --value "value" --yes

5) Verify env vars on the linked project

npx vercel env ls production --scope prologe
npx vercel env ls preview --scope prologe
npx vercel env ls development --scope prologe

Never paste real secret values or real production identifiers into this skill. Use placeholders in examples and provide the actual value only at execution time.

OpenWork Defaults

Team scope / team id to use: prologe
Default landing project: openwork-landing
Use the app directory you actually want to affect before linking; for landing this is usually _repos/openwork/ee/apps/landing or the equivalent worktree path.

Common Gotchas

Always point to team id prologe when working on OpenWork Vercel config.
vercel may not be globally installed; npx vercel ... is the safe default.
vercel env ls and vercel env add expect the current directory to be linked to the target project.
For preview env vars across all branches, pass an empty third positional branch argument: preview "".
If Vercel says the codebase is not linked, run npx vercel link --yes --scope prologe --project openwork-landing first.

First-Time Setup (If Not Configured)

Confirm Vercel auth works:

npx vercel whoami

Change into the target app directory.
Link it to the OpenWork project using scope prologe.
Add env vars for the environments you need.
Verify with npx vercel env ls ....

Example: app feedback template id

npx vercel link --yes --scope prologe --project openwork-landing
npx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK production --scope prologe --value "<transactional-id>" --yes
npx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK preview "" --scope prologe --value "<transactional-id>" --yes
npx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK development --scope prologe --value "<transactional-id>" --yes

---name: vercel-env-varsdescription: Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"---## Quick Usage (Already Configured)### 1) Check Vercel access```bashnpx vercel whoaminpx vercel teams ls```### 2) Link the local app directory to the target project```bashnpx vercel link --yes --scope prologe --project openwork-landing```### 3) Add an env var to production```bashnpx vercel env add MY_ENV_VAR production --scope prologe --value "value" --yes```### 4) Add the same env var to preview and development```bashnpx vercel env add MY_ENV_VAR preview "" --scope prologe --value "value" --yesnpx vercel env add MY_ENV_VAR development --scope prologe --value "value" --yes```### 5) Verify env vars on the linked project```bashnpx vercel env ls production --scope prologenpx vercel env ls preview --scope prologenpx vercel env ls development --scope prologe```Never paste real secret values or real production identifiers into this skill.Use placeholders in examples and provide the actual value only at execution time.## OpenWork Defaults- Team scope / team id to use: `prologe`- Default landing project: `openwork-landing`- Use the app directory you actually want to affect before linking; for landing this is usually `_repos/openwork/ee/apps/landing` or the equivalent worktree path.## Common Gotchas- Always point to team id `prologe` when working on OpenWork Vercel config.- `vercel` may not be globally installed; `npx vercel ...` is the safe default.- `vercel env ls` and `vercel env add` expect the current directory to be linked to the target project.- For preview env vars across all branches, pass an empty third positional branch argument: `preview ""`.- If Vercel says the codebase is not linked, run `npx vercel link --yes --scope prologe --project openwork-landing` first.## First-Time Setup (If Not Configured)1. Confirm Vercel auth works:```bashnpx vercel whoami```2. Change into the target app directory.3. Link it to the OpenWork project using scope `prologe`.4. Add env vars for the environments you need.5. Verify with `npx vercel env ls ...`.## Example: app feedback template id```bashnpx vercel link --yes --scope prologe --project openwork-landingnpx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK production --scope prologe --value "<transactional-id>" --yesnpx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK preview "" --scope prologe --value "<transactional-id>" --yesnpx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK development --scope prologe --value "<transactional-id>" --yes```

Frequently asked questions