Back to catalog / Developer tools
Deploy to Vercel: preview by default
Checks project linkage, CLI identity, and team scope before choosing an authorized preview or production deployment path.
Skills
This skill lays out a decision path from a local project to Vercel: inspect the Git remote, `.vercel` linkage, CLI authentication, and team scope, then choose Git-integrated deployment, CLI deployment, or a documented fallback. Preview is the default. Use the production path only when the user explicitly requests production. Deployment uploads project files and changes an external service, so inspect the upload scope, account/team, and target first; keep credentials out of commands and logs. Installing the CLI or signing in does not authorize a production release, and linking a project creates an external association.
Permissions
Prerequisites
- A project directory and the Vercel CLI; some paths require an authenticated account and project-link files.
Permissions
- Reads project and Vercel configuration and uses the network and authenticated CLI to upload or link a project. Review upload scope; preview is default, and production requires an explicit request.
Limitations
Run deployment steps only when deployment is requested and authorized; CLI and account flows vary by the user setup.
Pinned upstream source
- Repository
- vercel-labs/agent-skills
- File path
- skills/deploy-to-vercel/SKILL.md
- Pinned commit
063bee94c3f4df8453406c830b0a7df0f2860278- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Codex · Claude Code · Gemini CLI · GitHub Copilot · Cursor · Windsurf · Cline · OpenCode
Main topic
Take a coding Agent change from context to verification