name	vercel-deploy
description	Deploy web projects to Vercel with automated CLI setup, authentication, and deployment configuration.
version	1.0.0
author	DunCrew
metadata	{"openclaw":{"emoji":"🔧","primaryEnv":"shell"}}

Vercel Deploy

Description

Deploy web projects to Vercel with automated CLI setup, authentication, and deployment configuration.

Instructions

Check Prerequisites
- Verify Node.js is installed (node --version)
- Check if Vercel CLI is installed (vercel --version)
- If not installed, run: npm i -g vercel
Verify Project Configuration
- Check for package.json with build scripts
- Verify vercel.json exists (optional, for custom config)
- Check for .env or .env.local for environment variables
- Ensure .gitignore excludes sensitive files
Authenticate with Vercel
- Run vercel login if not authenticated
- Guide user through browser-based OAuth flow
- Verify login successful with vercel whoami
Configure Project (First Deploy) If this is the first deployment:
- Run vercel to initialize
- Select or create organization
- Set project name
- Configure framework preset (Next.js, React, etc.)
- Set build and output settings
Set Environment Variables If environment variables are needed:
```
vercel env add VARIABLE_NAME
```
Or bulk add from .env:
- Read .env file
- Add each variable with appropriate scope (Production, Preview, Development)
Deploy For preview deployment:
```
vercel
```
For production deployment:
```
vercel --prod
```
Verify Deployment
- Check deployment URL in output
- Open preview URL to verify
- Check build logs for errors: vercel logs
- Verify environment variables are set correctly
Post-Deployment
- Note the deployment URL
- If production, verify the production domain
- Set up custom domain if needed: vercel domains add

Examples

Deploy Next.js App:

# Install Vercel CLI
npm i -g vercel

# Login
vercel login

# Deploy preview
vercel

# Deploy production
vercel --prod

Add Environment Variables:

# Add single variable
vercel env add DATABASE_URL

# Add to production only
vercel env add API_KEY production

Notes

Never commit .env files with secrets
Use preview deployments for testing
Production deploys go to main domain
Set up GitHub integration for automatic deploys
Check Vercel dashboard for detailed logs

Más de este repositorio

mismo repositorio

canvas

FatBy/DunCrew

Display interactive HTML content, visualizations, dashboards, or games on connected OpenClaw nodes (Mac, iOS, Android). Supports live reloading, remote navigation, JS execution, and canvas snapshots for development, testing, and presentation scenarios.

2026-04-152

clawhub

FatBy/DunCrew

Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI.

2026-04-152

code-runner

FatBy/DunCrew

Execute shell commands and scripts on the user's local machine.

2026-04-152

image-understand

FatBy/DunCrew

多模态 AI 图片理解工具。将图片发送给支持 vision 的 LLM 模型，获取图片的语义理解和详细描述。可分析截图、设计稿、图表、报错信息等。

2026-04-152

memory-system

FatBy/DunCrew

Unified memory search and management system for retrieving, storing, and organizing information across daily logs, persistent memory, SOPs, and execution traces. Use this skill to recall past events, manage knowledge bases, update important notes, or filter historical data by tags and time ranges.

2026-04-152

ocr-extract

FatBy/DunCrew

智能 OCR 文字提取工具。从图片中识别文字，支持中英文混排、图像预处理（灰度化+二值化提升识别率）、表格结构还原为 Markdown 格式。

2026-04-152

Vercel Deploy

Description

Deploy web projects to Vercel with automated CLI setup, authentication, and deployment configuration.

Instructions

Check Prerequisites

Verify Node.js is installed (node --version)
Check if Vercel CLI is installed (vercel --version)
If not installed, run: npm i -g vercel

Verify Project Configuration

Check for package.json with build scripts
Verify vercel.json exists (optional, for custom config)
Check for .env or .env.local for environment variables
Ensure .gitignore excludes sensitive files

Authenticate with Vercel

Run vercel login if not authenticated
Guide user through browser-based OAuth flow
Verify login successful with vercel whoami

Configure Project (First Deploy) If this is the first deployment:

Run vercel to initialize
Select or create organization
Set project name
Configure framework preset (Next.js, React, etc.)
Set build and output settings

Set Environment Variables If environment variables are needed:

vercel env add VARIABLE_NAME

Or bulk add from .env:

Read .env file
Add each variable with appropriate scope (Production, Preview, Development)

Deploy For preview deployment:

vercel

For production deployment:

vercel --prod

Verify Deployment

Check deployment URL in output
Open preview URL to verify
Check build logs for errors: vercel logs
Verify environment variables are set correctly

Post-Deployment

Note the deployment URL
If production, verify the production domain
Set up custom domain if needed: vercel domains add

Examples

Deploy Next.js App:

# Install Vercel CLI npm i -g vercel # Login vercel login # Deploy preview vercel # Deploy production vercel --prod

Add Environment Variables:

# Add single variable vercel env add DATABASE_URL # Add to production only vercel env add API_KEY production

Notes

Never commit .env files with secrets

Use preview deployments for testing

Production deploys go to main domain

Set up GitHub integration for automatic deploys

Check Vercel dashboard for detailed logs