Localized reading guide
vercel-deployPurpose, usage and source
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".
Source retrieved:
- Source repository
- openai/skills
- SKILL.md
skills/.curated/vercel-deploy/SKILL.md- Repository stars
- 28,420
- Repository updated
- 2026-10-29
- Categories
- Automation
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
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".
How the upstream workflow works
Quick Start
Check whether the Vercel CLI is installed (no escalation for this check): If vercel is installed, run this (with a 10 minute timeout): Important: Use a 10 minute (600000ms) timeout for the deploy command since builds can take a while. If vercel is not installed, or if the CLI fails with "No existing credentials found", use the fallback method below.
Vercel Deploy
Deploy any project to Vercel instantly. Always deploy as preview (not production) unless the user explicitly asks for production.
Upstream passage · L6 ↗Fallback (No Auth)
If CLI fails with auth error, use the deploy script: The script handles framework detection, packaging, and deployment. It waits for the build to complete and returns JSON with previewUrl and claimUrl.
command -v vercelRequirements and setup
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).
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
49f948faa9258a0c61caceaf225e179651397431- Source SHA-256
f4a6cbfbb378a320fae179a79f727a881d19677e9b3db96ed49d2dc02a74fa46