Env Manager
bobmatnyc/claude-mpm
Environment variable validation, synchronization, and management across local development, CI/CD, and deployment platforms
Deploys and manages Vercel projects through the CLI using an access token from the environment or a .env file instead of interactive login.
Install Vercel CLI With Tokens
$ npx skills add vercel-labs/agent-skills --skill vercel-cli-with-tokens -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel-labs/agent-skills vercel-cli-with-tokens --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-labs/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vercel-cli-with-tokens .claude/skills/vercel-cli-with-tokens && 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 "vercel-cli-with-tokens" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/vercel-cli-with-tokens into .claude/skills/vercel-cli-with-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-cli-with-tokens", 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-labs/agent-skills/tree/main/skills/vercel-cli-with-tokensType 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-labs/agent-skills --skill vercel-cli-with-tokens -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel-labs/agent-skills vercel-cli-with-tokens --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vercel-cli-with-tokens .agents/skills/vercel-cli-with-tokens && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vercel-cli-with-tokens" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/vercel-cli-with-tokens into .agents/skills/vercel-cli-with-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-cli-with-tokens", 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-labs/agent-skills --skill vercel-cli-with-tokens -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel-labs/agent-skills vercel-cli-with-tokens --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vercel-cli-with-tokens .cursor/skills/vercel-cli-with-tokens && 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 "vercel-cli-with-tokens" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/vercel-cli-with-tokens into .cursor/skills/vercel-cli-with-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-cli-with-tokens", 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-labs/agent-skills.git --path skills/vercel-cli-with-tokens--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-labs/agent-skills --skill vercel-cli-with-tokens -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel-labs/agent-skills vercel-cli-with-tokens --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vercel-cli-with-tokens .gemini/skills/vercel-cli-with-tokens && 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 "vercel-cli-with-tokens" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/vercel-cli-with-tokens into .gemini/skills/vercel-cli-with-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-cli-with-tokens", 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-labs/agent-skills vercel-cli-with-tokensInstalls 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-labs/agent-skills --skill vercel-cli-with-tokens -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vercel-cli-with-tokens .github/skills/vercel-cli-with-tokens && 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 "vercel-cli-with-tokens" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/vercel-cli-with-tokens into .github/skills/vercel-cli-with-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-cli-with-tokens", 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-labs/agent-skills --skill vercel-cli-with-tokens -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-labs/agent-skills vercel-cli-with-tokens --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vercel-cli-with-tokens .opencode/skills/vercel-cli-with-tokens && 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 "vercel-cli-with-tokens" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/vercel-cli-with-tokens into .opencode/skills/vercel-cli-with-tokens/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vercel-cli-with-tokens", 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
vercel-cli-with-tokens- GitHub stars
- 32k
- Used in
- 7 other repos
- Token cost
- ~2.6k tokens
- SKILL.md length
- 980 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- None found
At a glance
Deploys and manages Vercel projects through the CLI using an access token from the environment or a .env file instead of interactive login.
- Works in 2 steps: Locate the Vercel Token → Locate the Project and Team
- Deploying to Vercel from a CI job or sandbox where interactive login is unavailable
- SKILL.md covers Step 1: Locate the Vercel Token, Step 2: Locate the Project and…, CLI Setup and Deploying a Project, plus 6 more sections
- Calls vercel, git and stripe; reaches vercel.com; needs VERCEL_TOKEN
What it does
The agent first locates a Vercel token, in order: a `VERCEL_TOKEN` already set in the environment, a `VERCEL_TOKEN` entry in a `.env` file, a differently named variable in `.env` that looks like a Vercel token (they typically start with `vca_`), or, if there is none, a request that you create one at vercel.com/account/tokens. Once the token is exported as `VERCEL_TOKEN` the CLI reads it natively, and the skill warns against passing it as a `--token` flag because that exposes it in shell history and process listings.
It then looks for the project and team, using `VERCEL_PROJECT_ID` and `VERCEL_ORG_ID` from the environment, which must be set together or the CLI errors, or extracting the team slug from a project URL, so the CLI can target the right project without `vercel link`. A CLI setup section follows but is cut off in the excerpt, so later steps such as deploying and managing environment variables are not described.
When your agent uses it
- Deploying to Vercel from a CI job or sandbox where interactive login is unavailable
- Adding environment variables to a Vercel project from the command line
- Pointing the Vercel CLI at a specific project and team by ID
Example prompts
- “Deploy this project to Vercel using the token in my .env file.”
- “Add DATABASE_URL to the production environment on Vercel without using vercel login.”
- “Point the Vercel CLI at https://vercel.com/my-team/my-project using my token.”
Requirements
- The Vercel CLI
- A Vercel access token, created at vercel.com/account/tokens
Workflow steps
2 steps, taken from the step headings in SKILL.md.
- Locate the Vercel Token
- Locate the Project and Team
What it can do on your machine
Read from SKILL.md and the folder at commit 063bee9. 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:
vercelgitstripenpm
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
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
VERCEL_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vercel CLI With Tokens loads about 2.6k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 980 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:25
### B) Token is in a `.env` file under `VERCEL_TOKEN` - NoteMentions a .env fileSKILL.md:28
grep '^VERCEL_TOKEN=' .env 2>/dev/null - NoteMentions a .env fileSKILL.md:34
ort VERCEL_TOKEN=$(grep '^VERCEL_TOKEN=' .env | cut -d= -f2-) - NoteMentions a .env fileSKILL.md:37
### C) Token is in a `.env` file under a different name - NoteMentions a .env fileSKILL.md:42
grep -i 'vercel' .env 2>/dev/null - NoteMentions a .env fileSKILL.md:48
VERCEL_TOKEN=$(grep '^<VARIABLE_NAME>=' .env | cut -d= -f2-) - NoteMentions a .env fileSKILL.md:77
# Or check .env - NoteMentions a .env fileSKILL.md:78
grep -i 'vercel' .env 2>/dev/null - NoteMentions a .env fileSKILL.md:244
# Pull env vars to local .env.local file - NoteMentions a .env fileSKILL.md:302
the user.** Look in the current env and `.env` files first.
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 980 words (~2,609 tokens).
“Deploy and manage projects on Vercel using the CLI with token-based authentication, without relying on vercel login.”
- name
- vercel-cli-with-tokens
- metadata.author
- vercel
- metadata.version
- 1.0.0
Files
Just SKILL.md in skills/vercel-cli-with-tokens of vercel-labs/agent-skills.
Open the folder on GitHubat commit 063bee9
Used in 7 other repositories
We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in vercel-labs/agent-skills, which our catalogue first saw on October 7, 2026.
- robotostudio/turbo-start-sanity.agents/skills/vercel-cli-with-tokens
- fujioky/reach.agents/skills/vercel-cli-with-tokens
- CraftOS-dev/CraftBotskills/vercel-cli-with-tokens
- aiskillstore/marketplaceskills/vercel-labs/vercel-cli-with-tokens
- Asymmetric-al/core.agents/skills/vercel-cli-with-tokens.claude/skills/vercel-cli-with-tokens+1 more
- sickn33/agentic-awesome-skillsskills/vercel-cli-with-tokensplugins/agentic-awesome-skills/skills/vercel-cli-with-tokens+1 more
- lingxling/awesome-skills-cnvercel-labs-agent-skills/skills/vercel-cli-with-tokensantigravity-awesome-skills/skills/vercel-cli-with-tokens+2 more
Compare with similar skills
Vercel CLI With Tokens 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 |
|---|---|---|---|---|---|---|
| Vercel CLI With Tokens this skillvercel-labs/agent-skills | 32k | 7 repos | ~2.6k | Automated safety check: Notes | None | |
| Env Managerbobmatnyc/claude-mpm | 155 | — | ~2k | Automated safety check: Notes | MIT | |
| CodFlow Storefront Vercel Deploybighadj22/codflow | 350 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Add Vercel to NanoClawnanocoai/nanoclaw | 31k | — | ~1.5k | Automated safety check: Warn | MIT | |
| Phase 9 Deploymentww-w-ai/bkit-claude-code | 601 | — | ~2.7k | Automated safety check: Notes | Apache-2.0 | |
| Memstack Deployment Railway Deploycwinvestments/memstack | 423 | — | ~2.1k | Automated safety check: Pass | Proprietary |
Similar skills
CodFlow Storefront Vercel Deploy
bighadj22/codflow
Runbook for deploying or redeploying the CodFlow Astro storefront to Vercel, with required environment variables, CLI or Git methods and checks afterwards.
Add Vercel to NanoClaw
nanocoai/nanoclaw
Gives NanoClaw agents the ability to deploy web apps to Vercel by installing the Vercel CLI in agent containers and wiring up credential injection through OneCLI.
Phase 9 Deployment
ww-w-ai/bkit-claude-code
Deploy to production — CI/CD pipelines, environment config, deployment strategies.
Memstack Deployment Railway Deploy
cwinvestments/memstack
A skill your agent uses when the user says 'deploy to Railway', 'Railway setup', 'railway-deploy', or needs to deploy a Node.js, Python, or Docker application to Railway with environment variables…
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.
More from vercel-labs/agent-skills
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Deploy to Vercel
vercel-labs/agent-skills
Deploys applications to Vercel as previews by default, picking a deploy method from the project's link state, git remote and team.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Related
Works with
Categories
Questions about Vercel CLI With Tokens
What does Vercel CLI With Tokens do?
Deploys and manages Vercel projects through the CLI using an access token from the environment or a .env file instead of interactive login. com/account/tokens. Once the token is exported as `VERCEL_TOKEN` the CLI reads it natively, and the skill warns against passing it as a `--token` flag because that exposes it in shell history and process listings.
When should I use Vercel CLI With Tokens?
Vercel CLI With Tokens fits situations like: deploying to Vercel from a CI job or sandbox where interactive login is unavailable; adding environment variables to a Vercel project from the command line; pointing the Vercel CLI at a specific project and team by ID.
How do I install Vercel CLI With Tokens in Claude Code?
Run `npx skills add vercel-labs/agent-skills --skill vercel-cli-with-tokens -a claude-code`. Or copy the skill folder (skills/vercel-cli-with-tokens in vercel-labs/agent-skills) into .claude/skills/vercel-cli-with-tokens in your project. Claude Code loads it when a task matches its description.
How do I install Vercel CLI With Tokens in Codex?
Run `npx skills add vercel-labs/agent-skills --skill vercel-cli-with-tokens -a codex`. Or copy the skill folder (skills/vercel-cli-with-tokens in vercel-labs/agent-skills) into .agents/skills/vercel-cli-with-tokens in your project. Codex loads it when a task matches its description.
Can I use Vercel CLI With Tokens 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-labs/agent-skills --skill vercel-cli-with-tokens -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vercel-cli-with-tokens, .gemini/skills/vercel-cli-with-tokens, .github/skills/vercel-cli-with-tokens and .opencode/skills/vercel-cli-with-tokens in your project.
What does Vercel CLI With Tokens need to run?
Going by SKILL.md and its folder, Vercel CLI With Tokens needs the command-line tools its instructions call (vercel, git, stripe and npm) and credentials named VERCEL_TOKEN. Our summary lists: The Vercel CLI; A Vercel access token, created at vercel.com/account/tokens.
Does Vercel CLI With Tokens access the network?
SKILL.md names 1 domain. In commands or code: vercel.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Vercel CLI With Tokens 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 Vercel CLI With Tokens use?
No licence was found for Vercel CLI With Tokens or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Vercel CLI With Tokens use?
About 2.6k tokens (SKILL.md is roughly 10k 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 Vercel CLI With Tokens?
Skills that share tags, products or a category with Vercel CLI With Tokens: Env Manager (bobmatnyc/claude-mpm, 155 stars), CodFlow Storefront Vercel Deploy (bighadj22/codflow, 350 stars), Add Vercel to NanoClaw (nanocoai/nanoclaw, 31k stars) and Phase 9 Deployment (ww-w-ai/bkit-claude-code, 601 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vercel CLI With Tokens?
vercel-labs (a GitHub organization, an official publisher) maintains it in vercel-labs/agent-skills, which has 32,103 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on August 28, 2026.
Source: vercel-labs/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.