Menü
Deploy applications to Vercel. Use when deploying to preview or production.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Discover, install, and configure Vercel Marketplace integrations (databases, auth, logging, etc.). Use when adding third-party services to a Vercel project.
Deploy, manage, and develop projects on Vercel from the command line
Generate and iterate on UIs/apps with Vercel v0 via the v0 Platform API. Use when building a frontend with v0, calling the v0 API/SDK, or spending v0 credits.
Set up Vercel CLI and configure project linking. Use when first connecting a project to Vercel.
| name | deploy |
| description | Deploy applications to Vercel. Use when deploying to preview or production. |
| allowed-tools | ["Bash"] |
| user_invocable | true |
Deploy the current project to Vercel (preview or production).
Check Vercel CLI is installed:
vercel --version
If missing: npm i -g vercel
Check project is linked:
ls .vercel/project.json 2>/dev/null || ls .vercel/repo.json 2>/dev/null || echo "NOT LINKED"
If not linked, run the setup skill first.
Check correct team:
vercel whoami
vercel deploy
Production deploys overwrite what users see — confirm with the user before
running. In a monorepo, cd into the specific project directory first so the
right project is targeted.
vercel --prod # single-project repo
# OR
cd apps/web && vercel --prod # monorepo: deploy one project
If vercel build was run first:
vercel deploy --prebuilt
vercel deploy --env KEY=value
/vercel:logs.references/domains-and-dns.md.vercel deploy after vercel build without --prebuilt — the build output is ignored.VERCEL_TOKEN env var.--yes to skip Vercel confirmation prompts — let them run.For full deployment reference, see references/deployment.md.