Deploy to Vercel

Deploys a project to Vercel, as a preview unless told otherwise, through the Vercel CLI or, without an account, a bundled script that uploads the folder and returns a preview link and a claim link. Use when you want a shareable deployment link fast.

DevOpsPack: OpenAI skills77 linesvercel-deploy
Author
Source
openai/skills/skills/.curated/vercel-deploy @ 49f948f
License
MIT · Copyright (c) 2026 Vercel

About this skill

What it does

The skill deploys a project to Vercel and returns the link. It deploys a preview unless you explicitly ask for production. If the Vercel CLI is installed (command -v vercel), the agent runs vercel deploy [path] -y with a ten-minute timeout, adding --prod only for production.

When the CLI is missing or has no credentials, the agent runs scripts/deploy.sh, which needs no Vercel account. The script copies the project to a temporary folder without node_modules, .git, .env and .env.*, detects the framework from package.json (over forty, from Next.js and Astro to Hono and Express), packs a tarball and posts it to codex-deploy-skills.vercel.sh. It polls the preview URL for up to five minutes and prints JSON with previewUrl and claimUrl; the claim URL moves the deployment into your own Vercel account. A lone HTML file without package.json is renamed to index.html.

The agent returns the links and is told not to fetch the deployed URL to check it. Besides SKILL.md and the script, the folder holds agents/openai.yaml, icons and Vercel's MIT licence.

When to use it, and when not

Use it for "deploy this and give me a link": a prototype, a demo, a preview to share.

On a private project, note that the fallback uploads everything except those four patterns, so a credentials.json or a key file would go too. SKILL.md says nothing about environment variables, domains or Git integration; set those up in Vercel yourself.

How to run it

The install command below puts the whole folder in place. The fallback needs a Bash shell with tar and curl. In a Codex sandbox only the deploy command, never the CLI check, is rerun with escalated permissions (sandbox_permissions=require_escalated) when network calls are blocked. The agent picks the skill up by its description; to call it yourself:

  • Claude Code: /vercel-deploy, or ask for the skill by name.
  • Codex: $vercel-deploy.
  • Cursor: type / in the Agent chat and pick vercel-deploy.

Example: /vercel-deploy Deploy this folder as a preview and give me the link.

OpenAI has marked openai/skills deprecated; our copy is pinned to a commit there, and as of November 2026 openai/plugins has no newer version of this skill.

How it differs from similar skills

Deploy to Vercel, Vercel Labs has a word-for-word identical description but a longer flow: it checks the Git remote and the project link first and steers you towards deploys by git push. The agent cannot tell the two apart, so install one. Vercel CLI with tokens works from an access token instead of a browser login and also manages environment variables, domains and logs.

Deploy to Netlify always needs a Netlify login, links the folder to a site and documents netlify.toml, redirects and functions; this skill is shorter and can deploy without an account. Deploy to Render deploys from Git, including services with databases and background workers. Web frameworks on Cloudflare Workers targets Cloudflare Workers and has no deploy command of its own: it leaves the commands to the Wrangler and cf skills. CI/CD pipeline setup builds a preview deploy per pull request into the pipeline instead of deploying from the chat.

Install

Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.

Claude Code — macOS, Linux
curl -fsSL --create-dirs -o ~/.claude/skills/vercel-deploy/SKILL.md https://anymodel.org/en/skills/openai/vercel-deploy/SKILL.md -o ~/.claude/skills/vercel-deploy/LICENSE.txt https://anymodel.org/en/skills/openai/vercel-deploy/LICENSE.txt -o ~/.claude/skills/vercel-deploy/agents/openai.yaml https://anymodel.org/en/skills/openai/vercel-deploy/agents/openai.yaml -o ~/.claude/skills/vercel-deploy/assets/vercel-small.svg https://anymodel.org/en/skills/openai/vercel-deploy/assets/vercel-small.svg -o ~/.claude/skills/vercel-deploy/assets/vercel.png https://anymodel.org/en/skills/openai/vercel-deploy/assets/vercel.png -o ~/.claude/skills/vercel-deploy/scripts/deploy.sh https://anymodel.org/en/skills/openai/vercel-deploy/scripts/deploy.sh
Codex, Cursor — macOS, Linux
curl -fsSL --create-dirs -o ~/.agents/skills/vercel-deploy/SKILL.md https://anymodel.org/en/skills/openai/vercel-deploy/SKILL.md -o ~/.agents/skills/vercel-deploy/LICENSE.txt https://anymodel.org/en/skills/openai/vercel-deploy/LICENSE.txt -o ~/.agents/skills/vercel-deploy/agents/openai.yaml https://anymodel.org/en/skills/openai/vercel-deploy/agents/openai.yaml -o ~/.agents/skills/vercel-deploy/assets/vercel-small.svg https://anymodel.org/en/skills/openai/vercel-deploy/assets/vercel-small.svg -o ~/.agents/skills/vercel-deploy/assets/vercel.png https://anymodel.org/en/skills/openai/vercel-deploy/assets/vercel.png -o ~/.agents/skills/vercel-deploy/scripts/deploy.sh https://anymodel.org/en/skills/openai/vercel-deploy/scripts/deploy.sh
Claude Code — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE.txt','agents/openai.yaml','assets/vercel-small.svg','assets/vercel.png','scripts/deploy.sh') { $p = Join-Path "$HOME\.claude\skills\vercel-deploy" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/openai/vercel-deploy/$f" -UseBasicParsing -OutFile $p }
Codex, Cursor — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE.txt','agents/openai.yaml','assets/vercel-small.svg','assets/vercel.png','scripts/deploy.sh') { $p = Join-Path "$HOME\.agents\skills\vercel-deploy" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/openai/vercel-deploy/$f" -UseBasicParsing -OutFile $p }

Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/openai/vercel-deploy/SKILL.md

SKILL.md

Raw

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?

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack OpenAI skills

ASP.NET Core apps

Guides the agent through current ASP.NET Core practice: choosing Blazor, Razor Pages, MVC or Minimal APIs, Program.cs and middleware order, auth, EF Core, tests and upgrades to .NET 10. Use when building, reviewing or upgrading an ASP.NET Core app.

ChatGPT Apps SDK

Builds ChatGPT apps on the Apps SDK: reads current OpenAI docs first, picks an app archetype, plans MCP tools, adapts an official example or scaffolds a Node server and widget, then tests in Developer Mode. Use when building or fixing an app inside ChatGPT.

CLI creator from API docs

Builds a durable CLI from API docs, an OpenAPI spec, curls or a script: JSON output, doctor and dry-run commands, safe auth, installed on PATH and paired with a companion skill. Use when an agent keeps hitting the same service through ad hoc calls.

Define a measurable goal

Turns a fuzzy intention into one measurable goal with a validator, scope and stop condition, then registers it via get_goal and create_goal. Use before goal-backed or long-running agent work, when "done" needs a number or a check.

Address GitHub PR comments

Fetches all comments, reviews and inline threads on the current branch's GitHub PR with a gh GraphQL script, numbers them and fixes only the ones you pick. Use when a PR has review comments to work through and you want to choose which get changed.

Fix failing GitHub Actions checks

Finds failing GitHub Actions checks on a PR with gh, pulls the logs, extracts the failure snippet and drafts a fix plan, changing code only after approval. Use when a PR's CI is red and you want the cause and a plan before any edit.

Jupyter notebooks

Creates and tidies Jupyter notebooks for experiments or tutorials from bundled templates via a stdlib script, with structure patterns and a run-top-to-bottom checklist. Use when starting a notebook or turning a messy one into something others can rerun.

Linear issues and projects

Works with Linear issues, projects and cycles through Linear's MCP server in a fixed order: setup, scope, read, then write, with sample workflows for triage, sprints and releases. Use when an agent should read or update Linear as part of a task.

Deploy to Netlify

Deploys the current project to Netlify with `npx netlify`: checks the login, links the folder to a site by Git remote or creates one, builds locally and returns a preview or production URL. Use when you want to publish a site to Netlify from your machine.

Browser automation with Playwright CLI

Drives a real browser from the terminal with playwright-cli: snapshots give element refs for clicks and typing, plus screenshots, console, network and traces, with no test files written. Use when a task needs a browser clicked through step by step.

Deploy to Render

Deploys an app to Render from a Git repo: writes and validates a render.yaml Blueprint with services, databases and secrets, or creates one service through the Render MCP server, then checks status and logs. Use when an app needs hosting on Render.

Security best-practice review

Checks Python, JavaScript/TypeScript and Go code against bundled security specs for ten frameworks, writes a report by severity with line numbers and fixes one finding at a time. Use when you explicitly ask for a security best-practice review.

Repository threat model

Writes a repository-grounded threat model: trust boundaries, assets, attacker capabilities and ranked abuse paths with mitigations, asking you to confirm key assumptions before the final file. Use when you explicitly ask to threat model a codebase.

Sentry issues and events

Reads Sentry issues and events through the sentry CLI without changing anything: recent production errors, issue and event details, AI root-cause summaries, with PII redacted. Use when you ask what is failing in production according to Sentry.

Figma MCP design context

Reads Figma frames through the Figma MCP server in a fixed order (design context, metadata, screenshot) and rebuilds them with the project's components and tokens; also covers server setup in Codex. Use when connecting Figma MCP or coding from a frame link.

Figma use_figma prerequisite

Sets the rules an agent must load before every use_figma call that runs Plugin API JavaScript in a Figma file: return values, page resets, colours, fonts, node IDs, small validated steps. Use when creating or editing anything inside a Figma file.

Implement a Figma design in code

Implements a Figma frame or component as code in your repo with 1:1 visual parity: fetches context and a screenshot, maps the output to project tokens and components, then runs a validation checklist. Use when a Figma link must become production UI.

Generate a Figma design from an app

Builds or updates a full screen in Figma from code or a description, section by section, using the file's published components, variables and styles instead of hardcoded values. Use when a page from your app should exist as a Figma screen.

Figma design system from a codebase

Builds a Figma design system library from a codebase in five supervised phases: discovery, variables and styles, page structure, components one by one, QA. Use when a product needs a Figma library that matches its code tokens and components.

Figma Code Connect components

Links published Figma components to the code components that implement them via Code Connect: finds unmapped ones, matches them in the codebase, maps only what the user approves. Use when a Figma library and its code both exist but are not linked.

Figma design system rules

Writes project rules for turning Figma designs into code into CLAUDE.md, AGENTS.md or a Cursor rules file, based on Figma's rule template and an analysis of the codebase. Use when setting up an agent for regular Figma-to-code work in a repo.

Create a new Figma file

Creates a blank Figma design file or FigJam board in your drafts, resolving the plan through whoami, and returns the file key and URL. Use when the next Figma step needs a fresh file to write into.