vercel-deploy

name	vercel-deploy
description	Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

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 without changing runtime permissions (for example, command -v vercel).
• Respect the current runtime permission and network policy. If deployment network calls are blocked, stop and report the blocker; ask the user to run in an environment where they have explicitly allowed Vercel network access.
• The deployment might take a few minutes. Use appropriate timeout values.

Quick Start

1. Check whether the Vercel CLI is installed (no escalation for this check):

command -v vercel

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

vercel deploy [path] -y

Important: Use a 10 minute (600000ms) 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="<path-to-skill>"

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

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

# Deploy existing tarball
bash "$skill_dir/scripts/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

Escalated Network Access

If deployment fails due to network issues (timeouts, DNS errors, connection resets), first distinguish provider/network failure from runtime policy blocking. When runtime policy blocks outbound deployment calls, do not weaken the policy from inside the skill. Do not change policy for the command -v vercel installation check.

Example guidance to the user:

The deploy needs Vercel network access, but the current runtime policy blocked it. Please approve network access or run this deploy from an environment where Vercel access is allowed.