sp-vercel

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying to Vercel from automated or agent-driven environments is difficult when interactive vercel login is unavailable, and passing tokens as CLI flags exposes secrets in shell history and process listings. ## Core Features & Use Cases - Token-Based Authentication: Locates VERCEL_TOKEN from the environment or .env files and exports it so the Vercel CLI reads it natively without --token flags. - Deployment Workflows: Supports quick deploys with VERCEL_PROJECT_ID/VERCEL_ORG_ID, full link-and-deploy flows with vercel link --repo, and git-push triggered deployments. - Project Management: Covers environment variable management, deployment inspection with logs, domain configuration, and Stripe Projects plan upgrades or downgrades. - Use Case: An AI agent in a CI-like environment needs to deploy a Next.js app to a Vercel team as a preview deployment using only a stored access token, without any interactive prompts. ## Quick Start Deploy my project to Vercel as a preview using the token in my environment.

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 a Vercel access token as the VERCEL_TOKEN environment variable and the CLI reads it natively. Create tokens at vercel.com/account/tokens, then run vercel deploy with your team scope.

How do I deploy a preview vs production build with Vercel CLI?

Run vercel deploy -y --no-wait for a preview deployment, which is the default behavior. Only add the --prod flag when production deployment is explicitly requested.

Can I pass the Vercel token as a --token CLI 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.

How do I add environment variables to a Vercel project?

Pipe the value into vercel env add, for example: echo "value" | vercel env add VAR_NAME --scope team-slug. You can target production, preview, or development environments, and list or remove variables with vercel env ls and vercel env rm.

Why does Vercel CLI authentication fail with a token?

The token may be expired or invalid. Verify it with vercel whoami, which uses VERCEL_TOKEN from the environment, and request a fresh token from the user if verification fails.

What are VERCEL_ORG_ID and VERCEL_PROJECT_ID used for?

Setting both variables lets the CLI target the correct project and team without vercel link or a .vercel directory. They must be set together, since setting only one causes an error.