Preview
Share a reviewable build
Ask for a preview URL so a teammate can inspect the change without targeting production.
01 / The skill · Deployment · Preview workflow
Deploy to Vercel: know what will go live, and where
A deployment Skill that checks repository and Vercel project state, chooses an appropriate path, and defaults to a preview unless production is explicitly requested.
Publisher, source, and installation
Published by Vercel Labs · Type: Deployment workflow Skill
Independent guide. Vercel Labs has not endorsed Floatboat.
Upstream installation
npx skills add vercel-labs/agent-skills --skill deploy-to-vercelThis installs agent instructions, not a Vercel account or a Floatboat deployment integration.
A realistic request
The original workflow starts with read-only checks for Git remote, project linkage, CLI authentication, and teams. It then selects a deployment route. A linked Git project may use a push, but the source requires asking before pushing.
Ask the agent
“Create a Vercel preview for this branch, confirm the linked project and team first, and do not push or deploy production without asking me.”
A useful result
A useful response reports the detected project state, selected preview path, any required approval, and the resulting URL when deployment succeeds.
When this deployment Skill is useful
Use it when the requested result is a Vercel preview or release, not merely a build check.
Linkage
The local folder may point to the wrong project
Check existing Vercel link files and Git remote before running any command that might silently connect a project.
Team
Several Vercel teams are available
Confirm the intended team or use the linked project's org ID instead of guessing an account scope.
Deployment decisions that still need you
- Implicit permission to push commits or deploy production; approval and environment choice still matter.
- A generic CI/CD guide for providers other than Vercel.
How it chooses a deployment path
The source begins with project-state checks, then uses the available linked Git or CLI path.
- 01
Check local state
Read the Git remote, Vercel link files, CLI authentication, and team list.
- 02
Select preview route
Use the linked workflow that matches the project; ask before any Git push.
- 03
Return and inspect URL
Confirm that the preview belongs to the intended project and actually loads.
02 / Practical guide
Preview first, with the right project and team
Deployment can change external state. The workflow checks linkage and scope before using Git or CLI, and distinguishes preview from production.
Does Deploy to Vercel publish to production by default?
No. The source says to deploy a preview unless the user explicitly asks for production. It also requires checking the current project and team before choosing a method.
Will it push code without asking?
The documented Git-push path requires the agent to ask before pushing. A Skill is guidance to the host agent, not a separate source of permission to change your repository.
What you can take away
- Confirmed project and team scope
- A preview deployment path
- A reviewable deployment URL when successful
What to check first
- Is the target preview or production?
- Was the Git push explicitly approved?
- Does the deployment belong to the correct project?
Explore More Agent Skills
Read another Skill guide and check its original source before using it.
Frequently Asked Questions
What does this Skill install?
It adds agent instructions. You still need appropriate Vercel access and a project that can be built and deployed.
Is preview deployment the default?
Yes. The source reserves production for an explicit user request.
Does it choose a Vercel team automatically?
A linked project can establish the team. If multiple unlinked teams are possible, the workflow asks which one is intended.
How is this different from Vercel CLI with Tokens?
Deploy to Vercel is the general deployment-decision workflow. Vercel CLI with Tokens focuses on authenticated CLI operations using an existing access token.
03 / Put it to work · Plan the release
Keep release decisions beside the work
Use Floatboat to review the change, intended environment, and approval trail before invoking an external deployment workflow.