Vercel Install Auth

What it does

When your agent uses it

• Setting up Vercel for the first time
• Creating access tokens
• Initializing a project with vercel link
• With phrases like install vercel

Example prompts

• “install vercel”
• “setup vercel”
• “vercel auth”
• “/vercel-install-auth”

Requirements

• Node.js
• A credential in VERCEL_TOKEN
• Compatibility (from SKILL.md): Designed for Claude Code
• Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(vercel:*), Grep

Workflow steps

6 steps, taken from the step headings in SKILL.md.

1. 1Install Vercel CLI
2. 2Authenticate — Interactive Login
3. 3Authenticate — Headless Token (CI/CD)
4. 4Link Local Project
5. 5Verify Connection via REST API
6. 6Pull Environment Variables

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Edit
  • Bash(npm:*)
  • Bash(npx:*)
  • Bash(vercel:*)
  • Grep

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • vercel
  • npm
  • curl
  • jq
  • npx

  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:

  • api.vercel.com

  Also links to:

  • 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.

• Compatibility

  Designed for Claude Code

  From compatibility in the SKILL.md frontmatter.

Context cost

Vercel Install Auth loads about 1.3k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 349 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~78

When it runs · the whole SKILL.md, loaded when a task matches

~1.3k

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

• NoteMentions a .env fileSKILL.md:116

  # Pull remote env vars to local .env.development.local

• NoteMentions a .env fileSKILL.md:117

  vercel env pull .env.development.local

• NoteMentions a .env fileSKILL.md:138

  - Environment variables pulled to local `.env.development.local`

• NoteRuns commands with sudoSKILL.md:146

  mission denied` | Global install without sudo | Use `npx vercel` or install with `--prefix ~/.npm-global` |

• NoteMentions a .env fileSKILL.md:155

  .env*.local

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

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 349 words, ~1,250 tokens.

name

vercel-install-auth

description

Install Vercel CLI and configure API token authentication. Use when setting up Vercel for the first time, creating access tokens, or initializing a project with vercel link. Trigger with phrases like "install vercel", "setup vercel", "vercel auth", "configure vercel token", "vercel login".

allowed-tools

Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(vercel:*), Grep

compatibility

Designed for Claude Code

version

1.18.0

license

MIT

author

Jeremy Longshore <jeremy@intentsolutions.io>

tags

saas, vercel, authentication, cli, setup

set -euo pipefail
# Global install (recommended)
npm install -g vercel@latest

# Or project-local
npm install --save-dev vercel@latest

# Verify installation
vercel --version

# Opens browser for OAuth login, stores token in ~/.config/com.vercel.cli
vercel login

# Or login with a specific email
vercel login your@email.com

# Login with GitHub
vercel login --github

# Login with GitLab
vercel login --gitlab

# Use a pre-created token — set as environment variable
export VERCEL_TOKEN="your-access-token-here"

# The CLI reads VERCEL_TOKEN automatically — no login needed
vercel whoami
# Output: your-username

# Scope the token to a specific team
export VERCEL_ORG_ID="team_xxxxxxxxxxxx"
export VERCEL_PROJECT_ID="prj_xxxxxxxxxxxx"

# Interactive — walks you through project selection
vercel link

# Or link to a specific project by name
vercel link --project my-project-name

# Verify the link — pulls .vercel/project.json
cat .vercel/project.json
# {"orgId":"team_xxx","projectId":"prj_xxx"}

# Test token against the REST API directly
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  https://api.vercel.com/v9/projects | jq '.projects[].name'

# List teams
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  https://api.vercel.com/v2/teams | jq '.teams[].name'

# Pull remote env vars to local .env.development.local
vercel env pull .env.development.local

# Pull for a specific environment
vercel env pull --environment=preview

# Vercel
.vercel/
.env*.local

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/.curated/vercel-install-auth of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287