vercel-deploy-1.0.0_skill

Overview

This skill deploys and manages Vercel projects with practical, script-driven operations. It provides commands to deploy to preview or production, manage environment variables, check deployment status, and view logs. The focus is on reliable infrastructure tasks—no promises of building your app for you. It supports both production and preview workflows.

How this skill works

The skill wraps Vercel CLI/API operations into simple scripts that use a VERCEL_TOKEN for authentication. Use provided scripts to deploy projects, list or set environment variables, query deployment status, and stream build or runtime logs. Operations require the project name or deployment ID and respect Vercel environments (preview vs production).

When to use it

• Deploy a new release to production or a preview environment.
• Add, update, or delete environment variables for a project.
• Check the status of the latest or a specific deployment.
• Fetch build or runtime logs to diagnose failures.
• Automate deploys from CI/CD or local scripts.

Best practices

• Store VERCEL_TOKEN in environment variables or a local .env file—not in source control.
• Prefer project-scoped tokens and rotate them regularly.
• Validate project names and account access before running scripts.
• Update environment variables, then trigger a deployment to pick up changes.
• Check build logs immediately after a failed deployment to locate errors.

Example use cases

• Initial testnet deployment: set RPC and contract environment variables, then deploy to production.
• Rotate a secret: update the env var via script, then redeploy to apply the new value.
• Debugging a failed build: fetch the deployment logs for the failing deployment ID.
• Preview testing: deploy a feature branch to a preview environment and share the URL.
• Automated pipeline: call the deploy script from CI to push production releases.