How do I install the Vercel Deploy skill?

Run npx skillmds@latest add kbarbel640-del/vercel-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vercel Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vercel Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vercel Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vercel Deploy?

kbarbel640-del (@kbarbel640-del) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vercel Deploy by kbarbel640-del — Agent Skill

Name: Vercel Deploy
Rating: 4.2 (5 reviews)
Author: kbarbel640-del

Vercel Deploy

Deploy and manage Vercel projects. Use when deploying applications to Vercel, managing environment variables, checking deployment status, viewing logs, or performing Vercel operations. Supports production and preview deployments. Practical infrastructure operations - no "AI will build your app" magic.

kbarbel640-del Updated Sep 8, 2026 1 repo stars

File contents

Vercel Deployment & Management

Deploy and manage Vercel projects. No "AI will build your app" nonsense - just practical Vercel operations.

Configuration

Vercel Setup

Get your token:

Go to https://vercel.com/account/tokens
Create token (name it "OpenClaw")
Set in environment:

export VERCEL_TOKEN="your-token-here"

Or store in .env:

VERCEL_TOKEN=your-token-here

Vercel Operations

Deploy Project

# Deploy to preview
scripts/vercel_deploy.sh --project bountylock --preview

# Deploy to production
scripts/vercel_deploy.sh --project bountylock --production

Manage Environment Variables

# List env vars
scripts/vercel_env.sh --project bountylock --list

# Set env var
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_RPC_URL \
  --value "https://sepolia.base.org" \
  --env production

# Delete env var
scripts/vercel_env.sh --project bountylock --delete \
  --key OLD_VAR \
  --env production

Check Deployment Status

# Get latest deployment
scripts/vercel_status.sh --project bountylock

# Get specific deployment
scripts/vercel_status.sh --deployment dpl_abc123

View Logs

# Get deployment logs
scripts/vercel_logs.sh --deployment dpl_abc123

# Get runtime logs
scripts/vercel_logs.sh --project bountylock --function api/bounties

Common Workflows

Initial Testnet Deployment

Set environment variables:

# Contract addresses (after deploying to Sepolia)
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_CONTRACT_ADDRESS \
  --value "0x..." \
  --env production

# RPC URL
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_RPC_URL \
  --value "https://sepolia.base.org" \
  --env production

# Chain ID
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_CHAIN_ID \
  --value "84532" \
  --env production

Deploy:

scripts/vercel_deploy.sh --project bountylock --production

Check status:

scripts/vercel_status.sh --project bountylock

Update Environment Variables

# Update contract address after redeployment
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_CONTRACT_ADDRESS \
  --value "0xNEW_ADDRESS" \
  --env production

# Trigger new deployment to use updated vars
scripts/vercel_deploy.sh --project bountylock --production

Debug Deployment Issues

# Get latest deployment info
scripts/vercel_status.sh --project bountylock

# Get build logs
scripts/vercel_logs.sh --deployment dpl_abc123

# Check environment variables
scripts/vercel_env.sh --project bountylock --list

Security Best Practices

Token Scope: Use project-scoped tokens when possible
Rotation: Rotate tokens periodically
Audit: Review deployment logs regularly
Secrets: Never commit tokens to git

Troubleshooting

"Authentication failed"

Check token is set correctly
Verify token hasn't expired

"Project not found"

Verify project name matches Vercel project
Check account has access to project

"Deployment failed"

Check build logs: scripts/vercel_logs.sh --deployment dpl_xxx
Verify environment variables are set correctly
Check for build errors in code

Reference Files

Vercel API Reference: See vercel-api.md for complete API documentation
Deployment Patterns: See deployment-patterns.md for common deployment workflows

---name: vercel-deploydescription: Deploy and manage Vercel projects. Use when deploying applications to Vercel, managing environment variables, checking deployment status, viewing logs, or performing Vercel operations. Supports production and preview deployments. Practical infrastructure operations - no "AI will build your app" magic.---# Vercel Deployment & ManagementDeploy and manage Vercel projects. No "AI will build your app" nonsense - just practical Vercel operations.## Configuration### Vercel Setup**Get your token:**1. Go to https://vercel.com/account/tokens2. Create token (name it "OpenClaw")3. Set in environment:```bashexport VERCEL_TOKEN="your-token-here"```Or store in `.env`:```VERCEL_TOKEN=your-token-here```## Vercel Operations### Deploy Project```bash# Deploy to previewscripts/vercel_deploy.sh --project bountylock --preview# Deploy to productionscripts/vercel_deploy.sh --project bountylock --production```### Manage Environment Variables```bash# List env varsscripts/vercel_env.sh --project bountylock --list# Set env varscripts/vercel_env.sh --project bountylock --set \ --key NEXT_PUBLIC_RPC_URL \ --value "https://sepolia.base.org" \ --env production# Delete env varscripts/vercel_env.sh --project bountylock --delete \ --key OLD_VAR \ --env production```### Check Deployment Status```bash# Get latest deploymentscripts/vercel_status.sh --project bountylock# Get specific deploymentscripts/vercel_status.sh --deployment dpl_abc123```### View Logs```bash# Get deployment logsscripts/vercel_logs.sh --deployment dpl_abc123# Get runtime logsscripts/vercel_logs.sh --project bountylock --function api/bounties```## Common Workflows### Initial Testnet Deployment1. **Set environment variables:**```bash# Contract addresses (after deploying to Sepolia)scripts/vercel_env.sh --project bountylock --set \ --key NEXT_PUBLIC_CONTRACT_ADDRESS \ --value "0x..." \ --env production# RPC URLscripts/vercel_env.sh --project bountylock --set \ --key NEXT_PUBLIC_RPC_URL \ --value "https://sepolia.base.org" \ --env production# Chain IDscripts/vercel_env.sh --project bountylock --set \ --key NEXT_PUBLIC_CHAIN_ID \ --value "84532" \ --env production```2. **Deploy:**```bashscripts/vercel_deploy.sh --project bountylock --production```3. **Check status:**```bashscripts/vercel_status.sh --project bountylock```### Update Environment Variables```bash# Update contract address after redeploymentscripts/vercel_env.sh --project bountylock --set \ --key NEXT_PUBLIC_CONTRACT_ADDRESS \ --value "0xNEW_ADDRESS" \ --env production# Trigger new deployment to use updated varsscripts/vercel_deploy.sh --project bountylock --production```### Debug Deployment Issues```bash# Get latest deployment infoscripts/vercel_status.sh --project bountylock# Get build logsscripts/vercel_logs.sh --deployment dpl_abc123# Check environment variablesscripts/vercel_env.sh --project bountylock --list```## Security Best Practices1. **Token Scope:** Use project-scoped tokens when possible2. **Rotation:** Rotate tokens periodically3. **Audit:** Review deployment logs regularly4. **Secrets:** Never commit tokens to git## Troubleshooting**"Authentication failed"**- Check token is set correctly- Verify token hasn't expired**"Project not found"**- Verify project name matches Vercel project- Check account has access to project**"Deployment failed"**- Check build logs: `scripts/vercel_logs.sh --deployment dpl_xxx`- Verify environment variables are set correctly- Check for build errors in code## Reference Files- **Vercel API Reference:** See [vercel-api.md](references/vercel-api.md) for complete API documentation- **Deployment Patterns:** See [deployment-patterns.md](references/deployment-patterns.md) for common deployment workflows

Frequently asked questions