ChatGPT Codex CLI OpenAI Skill

vercel-deploy

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

LLM Mart · 0 points · 24 views 0 listing impressions 0 install-command copies
Download openai-skills-skills_.curated_vercel-deploy-49f948f.zip · 6 KB

Install

skills CLI npx skills add https://github.com/openai/skills/tree/main/skills/.curated/vercel-deploy
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install openai-skills@llmmart
Git git clone https://github.com/openai/skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole openai/skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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?
Files (skills)
  • agents
    • openai.yaml 306 B
      Loading…
  • assets
    • vercel-small.svg 243 B · in bundle
    • vercel.png 788 B · in bundle
  • scripts
    • deploy.sh 8.7 KB
      Loading…
  • LICENSE.txt 1 KB
    Loading…
  • SKILL.md 2.6 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
    
    - 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):
    
    ```bash
    command -v vercel
    ```
    
    2. If `vercel` is installed, 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.
    
    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:
    
    ```bash
    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:
    ```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 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?
    ```
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.