Index of every page on this site: llms.txt
All skills
openai avatar

/vercel-deploy

@49f948f official
by openaiopenai/skills29k stars
2,023
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/openai/skills/vercel-deploy

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈52 tokens for metadata: the name and description. ≈604 when used: this file. ≈77 more on demand in 1 file.

Description uses 2.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈210 characters, or 2.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 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

  1. Check whether the Vercel CLI is installed (no escalation for this check):
command -v vercel
  1. 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.

  1. 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), 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?

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides capabilities to deploy projects to Vercel using either the local Vercel CLI or an included fallback deployment script. The execution and network patterns observed are consistent with standard deployment workflows, and the skill includes proactive exclusions to protect sensitive files.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: CRITICAL · 2 issues

  • Runlayer9mo

    4/4 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 49f948f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 9 months ago
  • CLI
  • vercel
  • deployment
  • preview
  • production
  • hosting
  • javascript
  • nodejs

README badge

README badge for openai/skills/vercel-deploy

Deploys applications to Vercel using the CLI or a fallback script, defaulting to preview deployments unless production is explicitly requested. Handles framework detection, manages authentication, and returns deployment and claim URLs.

Generated from the current SKILL.md.

Does this skill deploy to production by default?
No. The skill always deploys as a preview deployment unless you explicitly request production. Use --prod only when you ask for a production deploy.
What happens if the Vercel CLI is not installed?
The skill falls back to a deploy script that handles framework detection, packaging, and deployment without requiring CLI credentials.
How long should I expect a deployment to take?
Deployments can take several minutes. The skill uses a 10-minute timeout for the deploy command to account for build time.
What does the skill return after a successful deployment?
For preview deployments, the skill returns a previewUrl. For fallback deployments, it also provides a claimUrl so you can manage the deployment on Vercel.
What should I do if the deployment fails due to network issues?
The skill can rerun the deploy command with escalated network permissions to bypass sandbox networking blocks. This is only needed if standard deployment attempts fail with timeouts or connection errors.

Generated from the current SKILL.md. These answers refresh after source changes.