playbooks

home / skills / openai / skills / vercel-deploy

vercel-deploy skill

/skills/.curated/vercel-deploy

This skill deploys projects to Vercel as previews and provides the deployment URL and claim link for management.

npx playbooks add skill openai/skills --skill vercel-deploy

Review the files below or copy the command above to add this skill to your agents.

Files (6)
SKILL.md
2.1 KB
---
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

- When sandboxing blocks the deployment network calls, rerun with `sandbox_permissions=require_escalated`.
- The deployment might take a few minutes. Use appropriate timeout values.

## Quick Start

**Just run this (with a 10 minute timeout):**
```bash
vercel deploy [path] -y
```

**Important:** Use a 10 minute (600000ms) timeout for the deploy command since builds can take a while.

If that fails with "No existing credentials found", use the fallback method below.

## Fallback (No Auth)

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

```bash
# Deploy current directory
bash scripts/deploy.sh

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

# Deploy existing tarball
bash 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:
```bash
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), rerun the deploy with escalated permissions (use `sandbox_permissions=require_escalated`). The deploy requires escalated network access when sandbox networking blocks outbound requests.

Example guidance to the user:

```
The deploy needs escalated network access to deploy to Vercel. I can rerun the command with escalated permissions—want me to proceed?
```

Overview

This skill deploys applications and websites to Vercel on demand. It always creates preview deployments by default and will perform production deploys only when explicitly requested. The skill handles CLI and scripted fallback flows and returns the deployment links to the user.

How this skill works

The skill runs the Vercel CLI deploy command (vercel deploy [path] -y) with an extended timeout to accommodate builds. If CLI authentication fails, it falls back to a deploy script that packages the project, detects the framework, uploads a tarball, waits for the build, and returns JSON with previewUrl and claimUrl. It does not validate the deployed URL by fetching it; it simply returns the link(s).

When to use it

  • When the user asks to deploy an app or site (e.g., 'deploy my app', 'push this live')
  • When the user requests a preview deployment or a preview URL
  • When the user needs a quick preview for review or QA
  • When the user explicitly requests a production deploy
  • When CLI auth fails and a fallback scripted deploy is acceptable

Best practices

  • Always default to preview deploys unless the user explicitly requests --prod
  • Use a 10 minute timeout for the deploy command to avoid premature termination
  • If sandbox networking blocks the deploy, rerun with sandbox_permissions=require_escalated
  • When CLI returns 'No existing credentials found', use the fallback deploy script
  • Return only the deployment URL(s) and avoid curling or otherwise verifying the site

Example use cases

  • Create a preview deployment for a pull request so reviewers can test changes
  • Deploy a static site quickly and provide the previewUrl to a product manager
  • Fallback deploy a project when CI environment lacks Vercel credentials
  • Perform a production deploy after the user explicitly requests it
  • Re-run a failed deploy with escalated network permissions when sandbox blocks outbound calls

FAQ

What if deployment takes too long or times out?

Deployments can take several minutes. Use a 10 minute (600000 ms) timeout and rerun with escalated permissions if network issues persist.

What happens if the CLI reports no credentials?

The skill falls back to a scripted deploy that packages the project, uploads it, and returns previewUrl and claimUrl for management.

Do you verify the deployed site is working?

No—the skill does not curl or fetch the deployed URL. It returns the URL(s) provided by the deploy process.