deploy-to-vercel

SKILL.md

Deploy applications and websites to Vercel with automatic git integration and preview URLs.

Supports three deployment paths: git-push (ideal for linked projects), direct CLI deployment, and no-auth fallback for sandboxed environments

Automatically detects project state (linked via .vercel/project.json or .vercel/repo.json, git remote presence, CLI authentication) and chooses the best deployment method

Handles team selection for multi-team accounts and uses --scope to deploy to the correct team

Provides preview URLs for all deployments; linked projects with git remotes enable automatic deployments on future pushes

Includes fallback scripts for claude.ai and Codex sandboxes that require no authentication, returning both preview and claim URLs

Deploy to Vercel

Deploy any project to Vercel. Always deploy as preview (not production) unless the user explicitly asks for production.

The goal is to get the user into the best long-term setup: their project linked to Vercel with git-push deploys. Every method below tries to move the user closer to that state.

Step 1: Gather Project State

Run all four checks before deciding which method to use:

# 1. Check for a git remote
git remote get-url origin 2>/dev/null

# 2. Check if locally linked to a Vercel project (either file means linked)
cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null

# 3. Check if the Vercel CLI is installed and authenticated
vercel whoami 2>/dev/null