
vercel-deploy
✓ Official★ 23,200by openai · part of openai/skills
Deploy applications to Vercel as preview or production environments. Supports both Vercel CLI and fallback script-based deployment methods, with automatic framework detection and packaging Always deploys as preview by default unless user explicitly requests production deployment Returns preview URL immediately and claim URL for fallback deployments to manage the deployment Requires 10-minute timeout for build completion; escalates network permissions only if sandbox blocks outbound...
Deploy applications to Vercel as preview or production environments. Supports both Vercel CLI and fallback script-based deployment methods, with automatic framework detection and packaging Always deploys as preview by default unless user explicitly requests production deployment Returns preview URL immediately and claim URL for fallback deployments to manage the deployment Requires 10-minute timeout for build completion; escalates network permissions only if sandbox blocks outbound...
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.
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.
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.tgzThe 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."
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.
npx skills add https://github.com/openai/skills --skill vercel-deployRun this in your project — your agent picks the skill up automatically.
Prerequisites
- Check whether the Vercel CLI is installed without escalated permissions (for example,
command -v vercel). - Only escalate the actual deploy command if sandboxing blocks the deployment network calls (
sandbox_permissions=require_escalated). - The deployment might take a few minutes. Use appropriate timeout values.
Quick Start
- Check whether the Vercel CLI is installed (no escalation for this check):
command -v vercel- If
vercelis installed, run this (with a 10 minute timeout):
vercel deploy [path] -yImportant: Use a 10 minute (600000ms) timeout for the deploy command since builds can take a while.
- If
vercelis not installed, or if the CLI fails with "No existing credentials found", use the fallback method below.
Production Deploys
Only if user explicitly asks:
vercel deploy [path] --prod -yTroubleshooting
Escalated Network Access
If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the actual deploy command with escalated permissions (use sandbox_permissions=require_escalated). Do not escalate the command -v vercel installation check. 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?