Vercel Deploy

Vercel Deploy

Deploy any project to Vercel instantly. Always deploy as preview (not production) unless the user explicitly asks for production.

Prerequisites

• Check whether the Vercel CLI is installed (command -v vercel).
• The deployment might take a few minutes. Use appropriate timeout values.

Quick Start

1. Check whether the Vercel CLI is installed:

command -v vercel

2. If vercel is installed, run this (with a 10 minute timeout):

vercel deploy [path] -y

Important: Use a 10 minute (600s) timeout for the deploy command since builds can take a while.

3. If vercel is not installed, or if the CLI fails with "No existing credentials found", use the fallback method below.

Fallback (No Auth)

If CLI fails with auth error, use the deploy script:

skill_dir="$OPENCLAW_SKILL_DIR"

# Deploy current directory
bash "$skill_dir/deploy.sh"

# Deploy specific project
bash "$skill_dir/deploy.sh" /path/to/project

# Deploy existing tarball
bash "$skill_dir/deploy.sh" /path/to/project.tgz

The script handles framework detection, packaging, and deployment. It waits for the build to complete and returns JSON with previewUrl and claimUrl.

Tell the user: "Your deployment is ready at [previewUrl]. Claim it at [claimUrl] to manage your deployment."

Production Deploys

Only if user explicitly asks:

vercel deploy [path] --prod -y

Output

Show the user the deployment URL. For fallback deployments, also show the claim URL.

Do not curl or fetch the deployed URL to verify it works. Just return the link.

Troubleshooting

Network Access

If deployment fails due to network issues (timeouts, DNS errors, connection resets), check network connectivity and retry.