Deploy and manage Vercel projects using CLI token-based authentication.
npx skills add https://github.com/ramizik/okta --skill sp-vercel-ramizik
Please help me install this Agent Skill. Skill: sp-vercel Source: https://github.com/ramizik/okta/tree/main/.agents/skills/sp-vercel Command: npx skills add https://github.com/ramizik/okta --skill sp-vercel-ramizik
vercel login is unavailable, and passing tokens as CLI flags leaks secrets into shell history. This Skill provides a complete token-based workflow for locating credentials, linking projects, deploying, and managing environment variables without interactive login. ## Core Features & Use Cases - Token Discovery and Setup: Locates VERCEL_TOKEN from the environment or .env files, exports it safely, and avoids exposing secrets via --token flags. - Project Linking and Deployment: Links projects via vercel link or VERCEL_ORG_ID/VERCEL_PROJECT_ID, then deploys previews by default with production only on explicit request. - Operational Management: Manages environment variables, inspects deployments and logs, handles domains, and guides Stripe Projects plan upgrades or downgrades. - Use Case: An AI agent in a CI-like session needs to deploy a Next.js app to a Vercel team. It finds the token in .env, exports it, links the project with vercel link --repo --scope my-team -y, and runs a preview deploy without any interactive prompts. ## Quick Start Ask the agent to deploy this project to Vercel as a preview using the token stored in the environment or .env file.High-intent search queries and answers about installing and using this skill.
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 for non-interactive deployments.
Run vercel link --repo --scope <team-slug> -y when a git remote exists, which creates .vercel/repo.json. Without a git remote, use vercel link --scope <team-slug> -y, or set VERCEL_ORG_ID and VERCEL_PROJECT_ID to skip linking entirely.
No, passing tokens via the --token flag exposes secrets in shell history and process listings. Export VERCEL_TOKEN as an environment variable instead and let the CLI read it automatically.
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 into a local .env.local file.
Authentication failures usually mean the token is expired, invalid, or not exported in the current shell. Verify with vercel whoami, check printenv VERCEL_TOKEN, and request a fresh token from vercel.com/account/tokens if needed.
Default to preview deployments with vercel deploy -y --no-wait so changes can be reviewed safely. Only run vercel deploy --prod when the user explicitly requests a production release.
global-osManage environment variables and OIDC tokens in Vercel projects.
korallisDeploy Next.js applications to Vercel with preview deployments and environment variables.
vinhnguyenn020325-cmdAutomate Vercel deployments and integrate with GitHub Actions, GitLab CI, and Bitbucket Pipelines.
brainbrewlabsPublishes documentation to GitHub Pages, Vercel, or Netlify from source docs and build outputs.