# Vercel Deploy

> Use when the user wants to deploy, publish, or preview a project on Vercel; prefer the Vercel CLI, default to preview deploys, and only promote to production when the user explicitly asks.

- Skill: `hebertzhu/vercel-deploy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hebertzhu/vercel-deploy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hebertzhu/vercel-deploy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: hebertzhu (https://skillmd.com/u/hebertzhu)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hebertzhu/vercel-deploy

---


# Vercel Deploy

## Intent
- Use for Vercel preview deploys, production deploys, and deployment-oriented review of build and framework settings.

## Default operating pattern
1. Check whether `vercel` is available; if not, fall back to `npx vercel` or tell the user what must be installed.
2. Verify authentication with the Vercel CLI before deploying, and guide the user through `vercel login` when credentials are missing.
3. Default to preview deployment with `vercel deploy -y`; use `--prod` only when the user explicitly wants a production release.
4. Inspect framework config, environment variables, and build output only when the deploy errors or the project shape is unclear.
5. Return the deployment URL and any follow-up actions from the CLI output; do not probe the deployed URL unless the user specifically asks for verification.

## Pack fit
- Included in: `deploy-ops`
- Keep the public skill focused on the official CLI flow rather than private fallback services or custom claim flows.

## Boundary
- Do not auto-promote to production from a preview-first request.
- Do not claim the deployment is healthy just because the CLI returned a URL.