sp-vercel

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

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Mushfiq2002/stack-cost --skill sp-vercel-mushfiq2002
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-vercel
Source: https://github.com/Mushfiq2002/stack-cost/tree/main/.agents/skills/sp-vercel
Command: npx skills add https://github.com/Mushfiq2002/stack-cost --skill sp-vercel-mushfiq2002

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vercel.

What problem does it solve? Deploying to Vercel from CI pipelines or agent environments often fails because the CLI expects interactive login. This Skill provides a complete workflow for locating Vercel tokens, linking projects, deploying, and managing environment variables without interactive authentication. ## Core Features & Use Cases - Token Discovery: Locates VERCEL_TOKEN from the environment or .env files, and exports it so the CLI reads it natively instead of exposing it via --token flags. - Deployment Workflows: Covers quick deploys with project IDs, full link-and-deploy flows with or without git remotes, and preview-first deployment defaults. - Project Management: Manages environment variables, domains, deployment inspection, build logs, and Stripe Projects plan upgrades or downgrades. - Use Case: An AI agent in a CI environment needs to deploy a Next.js app to a Vercel team. It finds VERCEL_TOKEN in .env, exports it, links the project with vercel link --repo --scope team-slug -y, and runs a preview deploy. ## Quick Start Ask the agent to deploy this project to Vercel as a preview using the token stored in the environment or .env file.

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, so no vercel login is needed. Then run vercel deploy -y --no-wait, optionally with --scope for a team.

How do I find my Vercel token in a project?

Check printenv VERCEL_TOKEN first, then grep for VERCEL_TOKEN or any vercel-related variable in .env files. Vercel tokens typically start with vca_. If none exist, create one at vercel.com/account/tokens.

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 and let the CLI read it automatically.

How do I link a local directory to a Vercel project?

With a git remote, run vercel link --repo --scope <team-slug> -y, which creates .vercel/repo.json. Without a remote, use vercel link --scope <team-slug> -y, or target a project by name with --project.

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

The token may be expired or invalid. Verify it with vercel whoami, which uses VERCEL_TOKEN from the environment. If it fails, ask for a fresh token from vercel.com/account/tokens.

How do I manage Vercel environment variables from the CLI?

Use vercel env add, ls, pull, and rm with a --scope flag. For example, pipe a value with echo "value" | vercel env add VAR_NAME production --scope <team-slug> to set a production variable.