sp-vercel

Deploy and manage Vercel projects using CLI token-based authentication.

3|2|Updated Aug 28, 2026
One-click install
npx skills add https://github.com/SumonMSelim/stacksmith --skill sp-vercel-sumonmselim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-vercel
Source: https://github.com/SumonMSelim/stacksmith/tree/main/.agents/skills/sp-vercel
Command: npx skills add https://github.com/SumonMSelim/stacksmith --skill sp-vercel-sumonmselim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vercel.

What problem does it solve? Deploying to Vercel from automated or agentic environments is blocked by interactive login flows and unclear token handling. This Skill provides a complete workflow for using the Vercel CLI with access tokens, covering token discovery, project linking, deployments, environment variables, and plan management without interactive prompts. ## Core Features & Use Cases - Token-Based Authentication: Locate VERCEL_TOKEN from the environment or .env files and export it so the CLI reads it natively, avoiding insecure --token flags. - Deployment Workflows: Deploy via quick deploy with project IDs, git push triggers, or CLI deploys after linking with vercel link, defaulting to preview deployments. - Project Management: Manage environment variables, inspect deployments and build logs, configure domains, and handle Stripe Projects plan upgrades or downgrades. - Use Case: An AI agent in a CI environment needs to deploy a Next.js app to a specific Vercel team. It finds the token in .env, exports VERCEL_ORG_ID and VERCEL_PROJECT_ID, and runs vercel deploy -y --no-wait without any interactive prompts. ## Quick Start Deploy my project to Vercel as a preview using the token in my .env file and the team scope from my project URL.

Frequently Asked Questions about sp-vercel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy to Vercel without interactive login?

Export VERCEL_TOKEN as an environment variable and the Vercel CLI reads it natively, skipping vercel login. Then run vercel deploy -y --no-wait, optionally with --scope for the team slug.

How do I set environment variables on Vercel from the CLI?

Pipe the value into vercel env add, for example: echo "value" | vercel env add VAR_NAME production --scope team-slug. Use vercel env ls to list variables and vercel env pull to sync them locally.

Should I pass the Vercel token with the --token flag?

No. Passing tokens via --token exposes them in shell history and process listings. Export VERCEL_TOKEN as an environment variable instead and let the CLI read it automatically.

What is the difference between vercel link and vercel link --repo?

vercel link --repo reads the git remote and connects to the matching Vercel project, creating .vercel/repo.json. Plain vercel link matches by directory name and creates .vercel/project.json, which is less reliable.

Why does my Vercel CLI deployment fail with an authentication error?

The token may be expired or invalid. Verify with vercel whoami, which uses VERCEL_TOKEN from the environment, and check printenv or .env files for the token. If invalid, create a fresh token at vercel.com/account/tokens.