Vercel CLI with Tokens
Deploy and manage Vercel projects via CLI using environment-variable tokens instead of interactive login
- What
- Deploy and manage Vercel projects via CLI using environment-variable tokens instead of interactive login
- Cost
- Free
- Needs
- a Vercel account with a deployment token; the Vercel CLI and (optionally) GitHub CLI
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — run the Vercel CLI without interactive login: read `VERCEL_TOKEN`, `VERCEL_PROJECT_ID`, and `VERCEL_ORG_ID` from the environment (`.env` or shell exports), never pass the token via `--token` (so it stays out of shell history and process listings), prompt the user for a token only when none exists, verify credentials by resolving the team/project context first, and run deploys and management commands with `--yes` and `VERCEL_FORCE_NO_BUILD_CACHE` where appropriate — plus an explicit secrets hygiene doctrine: use env vars, prefer masked or ephemeral tokens, flag CI-vs-local usage differences. Covers CI/CD with GitHub Actions and git-based deploy flows, and a build/deploy/debug toolkit. Distinct from the published Vercel fiches in the catalog (agent-browser and find-skills, both from vercel-labs): this one is about driving the official Vercel CLI with tokens for deploy-and-manage automation, not browser automation or skill discovery. No accounts beyond your own Vercel account or paid services required — the free tier works. By @vercel-labs, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Vercel CLI with Tokens is a free Muse skill that runs the Vercel CLI without interactive login, reading your token, project ID and organization ID from environment variables. It never passes the token via a flag, so it stays out of shell history and process listings, and it prompts you for a token only when none exists.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 063bee9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Vercel account with a deployment token; the Vercel CLI and (optionally) GitHub CLI Install "Vercel CLI with Tokens" for me. Deploy and manage Vercel projects via CLI using environment-variable tokens instead of interactive login. Repository: https://raw.githubusercontent.com/vercel-labs/agent-skills/063bee94c3f4df8453406c830b0a7df0f2860278/skills/vercel-cli-with-tokens/SKILL.md Pinned version: install the code at commit 063bee94c3f4df8453406c830b0a7df0f2860278 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the vercel-labs-vercel-cli-with-tokens skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "vercel-labs-vercel-cli-with-tokens". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 063bee9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.