Individual skill
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
skills-imported/vercel-cli-with-tokens/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytesSKILL.mdcore · 10,685 bytes
Read excerpt
# Vercel CLI with Tokens
Deploy and manage projects on Vercel using the CLI with token-based authentication, without relying on `vercel login`.
> **Muse adaptation note:** If no token is found and the user provides one, prefer the Secure Vault capture flow for storing it rather than having it pasted into chat. Never echo a token back in chat output.
## Step 1: Locate the Vercel Token
Before running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order:
### A) `VERCEL_TOKEN` is already set in the environment
```bash
printenv VERCEL_TOKEN