▲ deploy-vercel

Deploy projects to Vercel — build, preview, promote to production. Manage domains and env vars.

🦞 Pixeyo CuratedRequires: vercel✓ Read source below

Deploy web projects to Vercel using the official CLI. Supports preview deployments, production promotion, domain management, and environment variables.

When to Use

Use when the user asks to deploy a site, push to Vercel, check deployment status, manage Vercel domains, or set environment variables.

Prerequisites

The user must have the Vercel CLI installed and authenticated:

npm i -g vercel
vercel login

Deployment Workflow

1. Preview deployment (default — safe)

cd /path/to/project
vercel --yes

This creates a preview URL. Share it with the user for review.

2. Production deployment

Only after user confirms the preview looks good:

vercel --prod --yes

3. Deploy a specific directory

vercel ./dist --yes
vercel ./out --prod --yes

Environment Variables

vercel env ls

vercel env add VARIABLE_NAME

vercel env pull .env.local

Domain Management

vercel domains ls

vercel domains add example.com

vercel domains inspect example.com

Check Deployments

vercel ls

vercel inspect <deployment-url>

Response Format

After deployment, always provide:

✅ Deployment URL (preview or production)
⏱ Build time if visible
Any build errors or warnings in full

Rules

Always do a preview deployment first. Never go straight to production unless explicitly asked.
Confirm with the user before promoting to production.
If the build fails, show the full error log and suggest fixes.
Never hardcode secrets in commands — use vercel env add for sensitive values.
If vercel CLI is not found, guide the user through installation.

📥 Download All Skills (.zip)🧩 Skill Explorer

📄 View raw SKILL.md source

--- name: deploy-vercel description: "Deploy projects to Vercel — build, preview, promote to production. Manage domains and env vars." user-invocable: true metadata: openclaw: requires: bins: ["vercel"] author: "pixeyo" homepage: "https://openclawcheatsheet.com/skills" --- # deploy-vercel Deploy web projects to Vercel using the official CLI. Supports preview deployments, production promotion, domain management, and environment variables. ## When to Use Use when the user asks to deploy a site, push to Vercel, check deployment status, manage Vercel domains, or set environment variables. ## Prerequisites The user must have the Vercel CLI installed and authenticated: ```bash npm i -g vercel vercel login ``` ## Deployment Workflow ### 1. Preview deployment (default — safe) ```bash cd /path/to/project vercel --yes ``` This creates a preview URL. Share it with the user for review. ### 2. Production deployment Only after user confirms the preview looks good: ```bash vercel --prod --yes ``` ### 3. Deploy a specific directory ```bash vercel ./dist --yes vercel ./out --prod --yes ``` ## Environment Variables ```bash # List current env vars vercel env ls # Add a new env var (interactive) vercel env add VARIABLE_NAME # Pull env vars to local .env vercel env pull .env.local ``` ## Domain Management ```bash # List domains vercel domains ls # Add a custom domain vercel domains add example.com # Check domain status vercel domains inspect example.com ``` ## Check Deployments ```bash # List recent deployments vercel ls # Inspect a specific deployment vercel inspect <deployment-url> ``` ## Response Format After deployment, always provide: - ✅ Deployment URL (preview or production) - ⏱ Build time if visible - Any build errors or warnings in full ## Rules - Always do a preview deployment first. Never go straight to production unless explicitly asked. - Confirm with the user before promoting to production. - If the build fails, show the full error log and suggest fixes. - Never hardcode secrets in commands — use `vercel env add` for sensitive values. - If `vercel` CLI is not found, guide the user through installation.