Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/vercel-install-auth

@820dfc8
Run it yourself

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

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/vercel-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈78 tokens for metadata: the name and description. ≈1.1k when used: this file.

Description uses 3.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈312 characters, or 3.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Vercel Install & Auth

Overview

Install the Vercel CLI, create a scoped access token, and link your local project to a Vercel project. This skill covers both interactive login and headless CI token authentication via the REST API.

Prerequisites

  • Node.js 18+ installed
  • npm, pnpm, or yarn available
  • A Vercel account (hobby, pro, or enterprise)

Instructions

Step 1: Install Vercel CLI

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

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

# Verify installation
vercel --version

Step 2: Authenticate — Interactive Login

# 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

Step 3: Authenticate — Headless Token (CI/CD)

Create a token in the Vercel dashboard at Settings > Tokens or via the API:

# 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"

Step 4: Link Local Project

# 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"}

Step 5: Verify Connection via REST API

# 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'

Step 6: Pull Environment Variables

# 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

Token Scopes Reference

Scope Access Use Case
Full Account All projects, all teams Personal dev
Team-scoped One team only Team CI/CD
Project-scoped One project only Per-project automation

Tokens support optional expiration dates. Set short-lived tokens (90 days) for CI and rotate them on a schedule.

Output

  • Vercel CLI installed and on PATH
  • Authentication token stored or environment variable set
  • Local project linked to Vercel project via .vercel/project.json
  • Environment variables pulled to local .env.development.local

Error Handling

Error Cause Solution
Error: No token found Not logged in, no VERCEL_TOKEN Run vercel login or export VERCEL_TOKEN
Error: Invalid token Token expired or revoked Generate new token at vercel.com/account/tokens
EACCES permission denied Global install without sudo Use npx vercel or install with --prefix ~/.npm-global
Error: Team not found Wrong VERCEL_ORG_ID Check team ID in Vercel dashboard > Settings > General
fetch failed Network or proxy issue Check HTTPS_PROXY env var, ensure port 443 outbound

.gitignore Setup

# Vercel
.vercel/
.env*.local

Examples

Set up a least-privilege local CLI session

Install the CLI through the project package manager or npx, authenticate with the organization’s approved short-lived token mechanism, and run vercel link only after confirming the intended team and project ID. Keep .vercel/ and local environment files ignored, and use vercel env pull only into a local ignored file. Verify access with a non-destructive project inspection, then revoke any temporary token once setup is complete.

Resources

Next Steps

After successful auth, proceed to vercel-hello-world for your first deployment.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a secure and standard workflow for installing the Vercel CLI and managing authentication. It utilizes official package registries and API endpoints, and it correctly implements security best practices for handling sensitive credentials using environment variables and version control exclusions.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 3 months ago
What it can do
Reads files Edits files Runs commands
version
1.18.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "saas",
  "vercel",
  "authentication",
  "cli",
  "setup"
]
All 7 allowed tools
ReadWriteEditBash(npm:*)Bash(npx:*)Bash(vercel:*)Grep
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/vercel-install-auth