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:
Install
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://github.com/vercel-labs/agent-skills/blob/main/skills/vercel-cli-with-tokens/SKILL.md 1. Fetch the SKILL.md file for the vercel-labs-vercel-cli-with-tokens skill from the repository into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.