
Deploy To Vercel
- 98.7k installs
- 29.5k repo stars
- Updated July 24, 2026
- vercel-labs/agent-skills
deploy-to-vercel is an agent skill that automatically detects project frameworks and deploys to Vercel with optimal setup guidance.
About
Deploy applications to Vercel instantly with auto-framework detection. The skill checks your project state, selects the best deployment method (git push, CLI, or full setup), and returns preview and claim URLs for ownership transfer.
- Auto-detects 40+ frameworks from package.json
- Returns preview and claim URLs for ownership transfer
- Guides users toward git-integrated deployments
Deploy To Vercel by the numbers
- 98,732 all-time installs (skills.sh)
- +4,307 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #5 of 1,453 DevOps & CI/CD skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
deploy-to-vercel capabilities & compatibility
- Capabilities
- framework detection · automated deployment · url generation
- Works with
- vercel
- Use cases
- ci cd · devops
What deploy-to-vercel says it does
The goal is to get the user into the best long-term setup: their project linked to Vercel with git-push deploys.
npx skills add https://github.com/vercel-labs/agent-skills --skill deploy-to-vercelAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 98.7k |
|---|---|
| repo stars | ★ 29.5k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 24, 2026 |
| Repository | vercel-labs/agent-skills ↗ |
How do you deploy a local app to Vercel preview?
Deploy applications to Vercel with automatic framework detection and optimal setup guidance.
Who is it for?
Developers deploying full-stack applications and wanting reliable, automatic framework detection.
Skip if: Developers deploying to AWS, Fly.io, or self-hosted Docker without Vercel, or those requiring production promotion by default.
When should I use this skill?
User asks to deploy, push live, or deploy to production
What you get
Vercel-linked project, preview deployment URL, and git-push deploy workflow configured.
- live-preview-url
- claim-url
- deployed-application
By the numbers
- auto-detects 40+ frameworks
- excludes node_modules and .git from uploads
Files
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
# 4. List available teams (if authenticated)
vercel teams list --format json 2>/dev/nullTeam selection
If the user belongs to multiple teams, present all available team slugs as a bulleted list and ask which one to deploy to. Once the user picks a team, proceed immediately to the next step — do not ask for additional confirmation.
Pass the team slug via --scope on all subsequent CLI commands (vercel deploy, vercel link, vercel inspect, etc.):
vercel deploy [path] -y --no-wait --scope <team-slug>If the project is already linked (.vercel/project.json or .vercel/repo.json exists), the orgId in those files determines the team — no need to ask again. If there is only one team (or just a personal account), skip the prompt and use it directly.
About the `.vercel/` directory: A linked project has either:
.vercel/project.json— created byvercel link(single project linking). ContainsprojectIdandorgId..vercel/repo.json— created byvercel link --repo(repo-based linking). ContainsorgId,remoteName, and aprojectsarray mapping directories to Vercel project IDs.
Either file means the project is linked. Check for both.
Do NOT use vercel project inspect, vercel ls, or vercel link to detect state in an unlinked directory — without a .vercel/ config, they will interactively prompt (or with --yes, silently link as a side-effect). Only vercel whoami is safe to run anywhere.
Step 2: Choose a Deploy Method
Linked (.vercel/ exists) + has git remote → Git Push
This is the ideal state. The project is linked and has git integration.
1. Ask the user before pushing. Never push without explicit approval:
This project is connected to Vercel via git. I can commit and push to
trigger a deployment. Want me to proceed?2. Commit and push:
git add .
git commit -m "deploy: <description of changes>"
git pushVercel automatically builds from the push. Non-production branches get preview deployments; the production branch (usually main) gets a production deployment.
3. Retrieve the preview URL. If the CLI is authenticated:
sleep 5
vercel ls --format jsonThe JSON output has a deployments array. Find the latest entry — its url field is the preview URL.
If the CLI is not authenticated, tell the user to check the Vercel dashboard or the commit status checks on their git provider for the preview URL.
---
Linked (.vercel/ exists) + no git remote → vercel deploy
The project is linked but there's no git repo. Deploy directly with the CLI.
vercel deploy [path] -y --no-waitUse --no-wait so the CLI returns immediately with the deployment URL instead of blocking until the build finishes (builds can take a while). Then check on the deployment status with:
vercel inspect <deployment-url>For production deploys (only if user explicitly asks):
vercel deploy [path] --prod -y --no-wait---
Not linked + CLI is authenticated → Link first, then deploy
The CLI is working but the project isn't linked yet. This is the opportunity to get the user into the best state.
1. Ask the user which team to deploy to. Present the team slugs from Step 1 as a bulleted list. If there's only one team (or just a personal account), skip this step.
2. Once a team is selected, proceed directly to linking. Tell the user what will happen but do not ask for separate confirmation:
Linking this project to <team name> on Vercel. This will create a Vercel
project to deploy to and enable automatic deployments on future git pushes.3. If a git remote exists, use repo-based linking with the selected team scope:
vercel link --repo --scope <team-slug>This reads the git remote URL and matches it to existing Vercel projects that deploy from that repo. It creates .vercel/repo.json. This is much more reliable than vercel link (without --repo), which tries to match by directory name and often fails when the local folder and Vercel project are named differently.
If there is no git remote, fall back to standard linking:
vercel link --scope <team-slug>This prompts the user to select or create a project. It creates .vercel/project.json.
4. Then deploy using the best available method:
- If a git remote exists → commit and push (see git push method above)
- If no git remote →
vercel deploy [path] -y --no-wait --scope <team-slug>, thenvercel inspect <url>to check status
---
Not linked + CLI not authenticated → Install, auth, link, deploy
The Vercel CLI isn't set up at all.
1. Install the CLI (if not already installed):
npm install -g vercel2. Authenticate:
vercel loginThe user completes auth in their browser. If running in a non-interactive environment where login is not possible, skip to the no-auth fallback below.
3. Ask which team to deploy to — present team slugs from vercel teams list --format json as a bulleted list. If only one team / personal account, skip. Once selected, proceed immediately.
4. Link the project with the selected team scope (use --repo if a git remote exists, plain vercel link otherwise):
vercel link --repo --scope <team-slug> # if git remote exists
vercel link --scope <team-slug> # if no git remote5. Deploy using the best available method (git push if remote exists, otherwise vercel deploy -y --no-wait --scope <team-slug>, then vercel inspect <url> to check status).
---
No-Auth Fallback — claude.ai sandbox
When to use: Last resort when the CLI can't be installed or authenticated in the claude.ai sandbox. This requires no authentication — it returns a Preview URL (live site) and a Claim URL (transfer to your Vercel account).
bash /mnt/skills/user/deploy-to-vercel/resources/deploy.sh [path]Arguments:
path- Directory to deploy, or a.tgzfile (defaults to current directory)
Examples:
# Deploy current directory
bash /mnt/skills/user/deploy-to-vercel/resources/deploy.sh
# Deploy specific project
bash /mnt/skills/user/deploy-to-vercel/resources/deploy.sh /path/to/project
# Deploy existing tarball
bash /mnt/skills/user/deploy-to-vercel/resources/deploy.sh /path/to/project.tgzThe script auto-detects the framework from package.json, packages the project (excluding node_modules, .git, .env), uploads it, and waits for the build to complete.
Tell the user: "Your deployment is ready at [previewUrl]. Claim it at [claimUrl] to manage your deployment."
---
No-Auth Fallback — Codex sandbox
When to use: In the Codex sandbox where the CLI may not be authenticated. Codex runs in a sandboxed environment by default — try the CLI first, and fall back to the deploy script if auth fails.
1. Check whether the Vercel CLI is installed (no escalation needed for this check):
command -v vercel2. If `vercel` is installed, try deploying with the CLI:
vercel deploy [path] -y --no-wait3. If `vercel` is not installed, or the CLI fails with "No existing credentials found", use the fallback script:
skill_dir="<path-to-skill>"
# Deploy current directory
bash "$skill_dir/resources/deploy-codex.sh"
# Deploy specific project
bash "$skill_dir/resources/deploy-codex.sh" /path/to/project
# Deploy existing tarball
bash "$skill_dir/resources/deploy-codex.sh" /path/to/project.tgzThe script handles framework detection, packaging, and deployment. It waits for the build to complete and returns JSON with previewUrl and claimUrl.
Tell the user: "Your deployment is ready at [previewUrl]. Claim it at [claimUrl] to manage your deployment."
Escalated network access: Only escalate the actual deploy command if sandboxing blocks the network call (sandbox_permissions=require_escalated). Do not escalate the command -v vercel check.
---
Agent-Specific Notes
Claude Code / terminal-based agents
You have full shell access. Do NOT use the /mnt/skills/ path. Follow the decision flow above using the CLI directly.
For the no-auth fallback, run the deploy script from the skill's installed location:
bash ~/.claude/skills/deploy-to-vercel/resources/deploy.sh [path]The path may vary depending on where the user installed the skill.
Sandboxed environments (claude.ai)
You likely cannot run vercel login or git push. Go directly to the no-auth fallback — claude.ai sandbox.
Codex
Codex runs in a sandbox. Check if the CLI is available first, then fall back to the deploy script. Go to the no-auth fallback — Codex sandbox.
---
Output
Always show the user the deployment URL.
- Git push: Use
vercel ls --format jsonto find the preview URL. If the CLI isn't authenticated, tell the user to check the Vercel dashboard or commit status checks. - CLI deploy: Show the URL returned by
vercel deploy --no-wait. Usevercel inspect <url>to check build status and report it to the user. - No-auth fallback: Show both the preview URL and the claim URL:
Deployment successful!
Preview URL: https://my-app-abc123.vercel.app
Claim URL: https://vercel.com/claim-deployment?code=...
View your site at the Preview URL.
To transfer this deployment to your Vercel account, visit the Claim URL.Do not curl or fetch the deployed URL to verify it works. Just return the link.
---
Troubleshooting
Network Egress Error (claude.ai)
If deployment fails due to network restrictions on claude.ai, tell the user:
Deployment failed due to network restrictions. To fix this:
1. Go to https://claude.ai/settings/capabilities
2. Add *.vercel.com to the allowed domains
3. Try deploying againEscalated Network Access (Codex / sandboxed environments)
If deployment fails due to network issues (timeouts, DNS errors, connection resets) in a sandboxed environment, rerun with escalated permissions (sandbox_permissions=require_escalated). Do not escalate the initial CLI availability check — only escalate the actual deploy command.
Example guidance to the user:
The deploy needs escalated network access to deploy to Vercel. I can rerun
the command with escalated permissions — want me to proceed?CLI Auth Failure
If vercel login or vercel deploy fails with authentication errors, fall back to the no-auth deploy script (claude.ai or Codex variant, depending on the environment).
#!/bin/bash
# Vercel Deployment Script for Codex (via claimable deploy endpoint)
# Usage: ./deploy-codex.sh [project-path]
# Returns: JSON with previewUrl, claimUrl, deploymentId, projectId
set -euo pipefail
DEPLOY_ENDPOINT="https://codex-deploy-skills.vercel.sh/api/deploy"
# Detect framework from package.json
detect_framework() {
local pkg_json="$1"
if [ ! -f "$pkg_json" ]; then
echo "null"
return
fi
local content=$(cat "$pkg_json")
# Helper to check if a package exists in dependencies or devDependencies.
# Use exact matching by default, with a separate prefix matcher for scoped
# package families like "@remix-run/".
has_dep_exact() {
echo "$content" | grep -q "\"$1\""
}
has_dep_prefix() {
echo "$content" | grep -q "\"$1"
}
# Order matters - check more specific frameworks first
# Blitz
if has_dep_exact "blitz"; then echo "blitzjs"; return; fi
# Next.js
if has_dep_exact "next"; then echo "nextjs"; return; fi
# Gatsby
if has_dep_exact "gatsby"; then echo "gatsby"; return; fi
# Remix
if has_dep_prefix "@remix-run/"; then echo "remix"; return; fi
# React Router (v7 framework mode)
if has_dep_prefix "@react-router/"; then echo "react-router"; return; fi
# TanStack Start
if has_dep_exact "@tanstack/start"; then echo "tanstack-start"; return; fi
# Astro
if has_dep_exact "astro"; then echo "astro"; return; fi
# Hydrogen (Shopify)
if has_dep_exact "@shopify/hydrogen"; then echo "hydrogen"; return; fi
# SvelteKit
if has_dep_exact "@sveltejs/kit"; then echo "sveltekit-1"; return; fi
# Svelte (standalone)
if has_dep_exact "svelte"; then echo "svelte"; return; fi
# Nuxt
if has_dep_exact "nuxt"; then echo "nuxtjs"; return; fi
# Vue with Vitepress
if has_dep_exact "vitepress"; then echo "vitepress"; return; fi
# Vue with Vuepress
if has_dep_exact "vuepress"; then echo "vuepress"; return; fi
# Gridsome
if has_dep_exact "gridsome"; then echo "gridsome"; return; fi
# SolidStart
if has_dep_exact "@solidjs/start"; then echo "solidstart-1"; return; fi
# Docusaurus
if has_dep_exact "@docusaurus/core"; then echo "docusaurus-2"; return; fi
# RedwoodJS
if has_dep_prefix "@redwoodjs/"; then echo "redwoodjs"; return; fi
# Hexo
if has_dep_exact "hexo"; then echo "hexo"; return; fi
# Eleventy
if has_dep_exact "@11ty/eleventy"; then echo "eleventy"; return; fi
# Angular / Ionic Angular
if has_dep_exact "@ionic/angular"; then echo "ionic-angular"; return; fi
if has_dep_exact "@angular/core"; then echo "angular"; return; fi
# Ionic React
if has_dep_exact "@ionic/react"; then echo "ionic-react"; return; fi
# Create React App
if has_dep_exact "react-scripts"; then echo "create-react-app"; return; fi
# Ember
if has_dep_exact "ember-cli" || has_dep_exact "ember-source"; then echo "ember"; return; fi
# Dojo
if has_dep_exact "@dojo/framework"; then echo "dojo"; return; fi
# Polymer
if has_dep_prefix "@polymer/"; then echo "polymer"; return; fi
# Preact
if has_dep_exact "preact"; then echo "preact"; return; fi
# Stencil
if has_dep_exact "@stencil/core"; then echo "stencil"; return; fi
# UmiJS
if has_dep_exact "umi"; then echo "umijs"; return; fi
# Sapper (legacy Svelte)
if has_dep_exact "sapper"; then echo "sapper"; return; fi
# Saber
if has_dep_exact "saber"; then echo "saber"; return; fi
# Sanity
if has_dep_exact "sanity"; then echo "sanity-v3"; return; fi
if has_dep_prefix "@sanity/"; then echo "sanity"; return; fi
# Storybook
if has_dep_prefix "@storybook/"; then echo "storybook"; return; fi
# NestJS
if has_dep_exact "@nestjs/core"; then echo "nestjs"; return; fi
# Elysia
if has_dep_exact "elysia"; then echo "elysia"; return; fi
# Hono
if has_dep_exact "hono"; then echo "hono"; return; fi
# Fastify
if has_dep_exact "fastify"; then echo "fastify"; return; fi
# h3
if has_dep_exact "h3"; then echo "h3"; return; fi
# Nitro
if has_dep_exact "nitropack"; then echo "nitro"; return; fi
# Express
if has_dep_exact "express"; then echo "express"; return; fi
# Vite (generic - check last among JS frameworks)
if has_dep_exact "vite"; then echo "vite"; return; fi
# Parcel
if has_dep_exact "parcel"; then echo "parcel"; return; fi
# No framework detected
echo "null"
}
# Parse arguments
INPUT_PATH="${1:-.}"
# Create temp directory for packaging
TEMP_DIR=$(mktemp -d)
TARBALL="$TEMP_DIR/project.tgz"
STAGING_DIR="$TEMP_DIR/staging"
CLEANUP_TEMP=true
cleanup() {
if [ "$CLEANUP_TEMP" = true ]; then
rm -rf "$TEMP_DIR"
fi
}
trap cleanup EXIT
echo "Preparing deployment..." >&2
# Check if input is a .tgz file or a directory
FRAMEWORK="null"
if [ -f "$INPUT_PATH" ] && [[ "$INPUT_PATH" == *.tgz ]]; then
# Input is already a tarball, use it directly
echo "Using provided tarball..." >&2
TARBALL="$INPUT_PATH"
CLEANUP_TEMP=false
# Can't detect framework from tarball, leave as null
elif [ -d "$INPUT_PATH" ]; then
# Input is a directory, need to tar it
PROJECT_PATH=$(cd "$INPUT_PATH" && pwd)
# Detect framework from package.json
FRAMEWORK=$(detect_framework "$PROJECT_PATH/package.json")
# Stage files into a temporary directory to avoid mutating the source tree.
mkdir -p "$STAGING_DIR"
echo "Staging project files..." >&2
tar -C "$PROJECT_PATH" \
--exclude='node_modules' \
--exclude='.git' \
--exclude='.env' \
--exclude='.env.*' \
-cf - . | tar -C "$STAGING_DIR" -xf -
# Check if this is a static HTML project (no package.json)
if [ ! -f "$PROJECT_PATH/package.json" ]; then
# Find HTML files in root
HTML_FILES=$(find "$STAGING_DIR" -maxdepth 1 -name "*.html" -type f)
HTML_COUNT=$(printf '%s\n' "$HTML_FILES" | sed '/^$/d' | wc -l | tr -d '[:space:]')
# If there's exactly one HTML file and it's not index.html, rename it
if [ "$HTML_COUNT" -eq 1 ]; then
HTML_FILE=$(echo "$HTML_FILES" | head -1)
BASENAME=$(basename "$HTML_FILE")
if [ "$BASENAME" != "index.html" ]; then
echo "Renaming $BASENAME to index.html..." >&2
mv "$HTML_FILE" "$STAGING_DIR/index.html"
fi
fi
fi
# Create tarball from the staging directory
echo "Creating deployment package..." >&2
tar -czf "$TARBALL" -C "$STAGING_DIR" .
else
echo "Error: Input must be a directory or a .tgz file" >&2
exit 1
fi
if [ "$FRAMEWORK" != "null" ]; then
echo "Detected framework: $FRAMEWORK" >&2
fi
# Deploy
echo "Deploying..." >&2
RESPONSE=$(curl -s -X POST "$DEPLOY_ENDPOINT" -F "file=@$TARBALL" -F "framework=$FRAMEWORK")
# Check for error in response
if echo "$RESPONSE" | grep -q '"error"'; then
ERROR_MSG=$(echo "$RESPONSE" | grep -o '"error":"[^"]*"' | cut -d'"' -f4)
echo "Error: $ERROR_MSG" >&2
exit 1
fi
# Extract URLs from response
PREVIEW_URL=$(echo "$RESPONSE" | grep -o '"previewUrl":"[^"]*"' | cut -d'"' -f4)
CLAIM_URL=$(echo "$RESPONSE" | grep -o '"claimUrl":"[^"]*"' | cut -d'"' -f4)
if [ -z "$PREVIEW_URL" ]; then
echo "Error: Could not extract preview URL from response" >&2
echo "$RESPONSE" >&2
exit 1
fi
echo "Deployment started. Waiting for build to complete..." >&2
echo "Preview URL: $PREVIEW_URL" >&2
# Poll the preview URL until it returns a non-5xx response (5xx = still building)
MAX_ATTEMPTS=60 # 5 minutes max (60 * 5 seconds)
ATTEMPT=0
while [ $ATTEMPT -lt $MAX_ATTEMPTS ]; do
HTTP_STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$PREVIEW_URL")
if [ "$HTTP_STATUS" -eq 200 ]; then
echo "" >&2
echo "Deployment ready!" >&2
break
elif [ "$HTTP_STATUS" -ge 500 ]; then
# 5xx means still building/deploying
echo "Building... (attempt $((ATTEMPT + 1))/$MAX_ATTEMPTS)" >&2
sleep 5
ATTEMPT=$((ATTEMPT + 1))
elif [ "$HTTP_STATUS" -ge 400 ] && [ "$HTTP_STATUS" -lt 500 ]; then
# 4xx might be an error or the app itself returns 4xx - it's responding
echo "" >&2
echo "Deployment ready (returned $HTTP_STATUS)!" >&2
break
else
# Any other status, assume it's ready
echo "" >&2
echo "Deployment ready!" >&2
break
fi
done
if [ $ATTEMPT -eq $MAX_ATTEMPTS ]; then
echo "" >&2
echo "Warning: Timed out waiting for deployment, but it may still be building." >&2
fi
echo "" >&2
echo "Preview URL: $PREVIEW_URL" >&2
echo "Claim URL: $CLAIM_URL" >&2
echo "" >&2
# Output JSON for programmatic use
echo "$RESPONSE"
#!/bin/bash
# Vercel Deployment Script (via claimable deploy endpoint)
# Usage: ./deploy.sh [project-path]
# Returns: JSON with previewUrl, claimUrl, deploymentId, projectId
set -euo pipefail
DEPLOY_ENDPOINT="https://claude-skills-deploy.vercel.com/api/deploy"
# Detect framework from package.json
detect_framework() {
local pkg_json="$1"
if [ ! -f "$pkg_json" ]; then
echo "null"
return
fi
local content=$(cat "$pkg_json")
# Helper to check if a package exists in dependencies or devDependencies.
# Use exact matching by default, with a separate prefix matcher for scoped
# package families like "@remix-run/".
has_dep_exact() {
echo "$content" | grep -q "\"$1\""
}
has_dep_prefix() {
echo "$content" | grep -q "\"$1"
}
# Order matters - check more specific frameworks first
# Blitz
if has_dep_exact "blitz"; then echo "blitzjs"; return; fi
# Next.js
if has_dep_exact "next"; then echo "nextjs"; return; fi
# Gatsby
if has_dep_exact "gatsby"; then echo "gatsby"; return; fi
# Remix
if has_dep_prefix "@remix-run/"; then echo "remix"; return; fi
# React Router (v7 framework mode)
if has_dep_prefix "@react-router/"; then echo "react-router"; return; fi
# TanStack Start
if has_dep_exact "@tanstack/start"; then echo "tanstack-start"; return; fi
# Astro
if has_dep_exact "astro"; then echo "astro"; return; fi
# Hydrogen (Shopify)
if has_dep_exact "@shopify/hydrogen"; then echo "hydrogen"; return; fi
# SvelteKit
if has_dep_exact "@sveltejs/kit"; then echo "sveltekit-1"; return; fi
# Svelte (standalone)
if has_dep_exact "svelte"; then echo "svelte"; return; fi
# Nuxt
if has_dep_exact "nuxt"; then echo "nuxtjs"; return; fi
# Vue with Vitepress
if has_dep_exact "vitepress"; then echo "vitepress"; return; fi
# Vue with Vuepress
if has_dep_exact "vuepress"; then echo "vuepress"; return; fi
# Gridsome
if has_dep_exact "gridsome"; then echo "gridsome"; return; fi
# SolidStart
if has_dep_exact "@solidjs/start"; then echo "solidstart-1"; return; fi
# Docusaurus
if has_dep_exact "@docusaurus/core"; then echo "docusaurus-2"; return; fi
# RedwoodJS
if has_dep_prefix "@redwoodjs/"; then echo "redwoodjs"; return; fi
# Hexo
if has_dep_exact "hexo"; then echo "hexo"; return; fi
# Eleventy
if has_dep_exact "@11ty/eleventy"; then echo "eleventy"; return; fi
# Angular / Ionic Angular
if has_dep_exact "@ionic/angular"; then echo "ionic-angular"; return; fi
if has_dep_exact "@angular/core"; then echo "angular"; return; fi
# Ionic React
if has_dep_exact "@ionic/react"; then echo "ionic-react"; return; fi
# Create React App
if has_dep_exact "react-scripts"; then echo "create-react-app"; return; fi
# Ember
if has_dep_exact "ember-cli" || has_dep_exact "ember-source"; then echo "ember"; return; fi
# Dojo
if has_dep_exact "@dojo/framework"; then echo "dojo"; return; fi
# Polymer
if has_dep_prefix "@polymer/"; then echo "polymer"; return; fi
# Preact
if has_dep_exact "preact"; then echo "preact"; return; fi
# Stencil
if has_dep_exact "@stencil/core"; then echo "stencil"; return; fi
# UmiJS
if has_dep_exact "umi"; then echo "umijs"; return; fi
# Sapper (legacy Svelte)
if has_dep_exact "sapper"; then echo "sapper"; return; fi
# Saber
if has_dep_exact "saber"; then echo "saber"; return; fi
# Sanity
if has_dep_exact "sanity"; then echo "sanity-v3"; return; fi
if has_dep_prefix "@sanity/"; then echo "sanity"; return; fi
# Storybook
if has_dep_prefix "@storybook/"; then echo "storybook"; return; fi
# NestJS
if has_dep_exact "@nestjs/core"; then echo "nestjs"; return; fi
# Elysia
if has_dep_exact "elysia"; then echo "elysia"; return; fi
# Hono
if has_dep_exact "hono"; then echo "hono"; return; fi
# Fastify
if has_dep_exact "fastify"; then echo "fastify"; return; fi
# h3
if has_dep_exact "h3"; then echo "h3"; return; fi
# Nitro
if has_dep_exact "nitropack"; then echo "nitro"; return; fi
# Express
if has_dep_exact "express"; then echo "express"; return; fi
# Vite (generic - check last among JS frameworks)
if has_dep_exact "vite"; then echo "vite"; return; fi
# Parcel
if has_dep_exact "parcel"; then echo "parcel"; return; fi
# No framework detected
echo "null"
}
# Parse arguments
INPUT_PATH="${1:-.}"
# Create temp directory for packaging
TEMP_DIR=$(mktemp -d)
TARBALL="$TEMP_DIR/project.tgz"
STAGING_DIR="$TEMP_DIR/staging"
CLEANUP_TEMP=true
cleanup() {
if [ "$CLEANUP_TEMP" = true ]; then
rm -rf "$TEMP_DIR"
fi
}
trap cleanup EXIT
echo "Preparing deployment..." >&2
# Check if input is a .tgz file or a directory
FRAMEWORK="null"
if [ -f "$INPUT_PATH" ] && [[ "$INPUT_PATH" == *.tgz ]]; then
# Input is already a tarball, use it directly
echo "Using provided tarball..." >&2
TARBALL="$INPUT_PATH"
CLEANUP_TEMP=false
# Can't detect framework from tarball, leave as null
elif [ -d "$INPUT_PATH" ]; then
# Input is a directory, need to tar it
PROJECT_PATH=$(cd "$INPUT_PATH" && pwd)
# Detect framework from package.json
FRAMEWORK=$(detect_framework "$PROJECT_PATH/package.json")
# Stage files into a temporary directory to avoid mutating the source tree.
mkdir -p "$STAGING_DIR"
echo "Staging project files..." >&2
tar -C "$PROJECT_PATH" \
--exclude='node_modules' \
--exclude='.git' \
--exclude='.env' \
--exclude='.env.*' \
-cf - . | tar -C "$STAGING_DIR" -xf -
# Check if this is a static HTML project (no package.json)
if [ ! -f "$PROJECT_PATH/package.json" ]; then
# Find HTML files in root
HTML_FILES=$(find "$STAGING_DIR" -maxdepth 1 -name "*.html" -type f)
HTML_COUNT=$(printf '%s\n' "$HTML_FILES" | sed '/^$/d' | wc -l | tr -d '[:space:]')
# If there's exactly one HTML file and it's not index.html, rename it
if [ "$HTML_COUNT" -eq 1 ]; then
HTML_FILE=$(echo "$HTML_FILES" | head -1)
BASENAME=$(basename "$HTML_FILE")
if [ "$BASENAME" != "index.html" ]; then
echo "Renaming $BASENAME to index.html..." >&2
mv "$HTML_FILE" "$STAGING_DIR/index.html"
fi
fi
fi
# Create tarball from the staging directory
echo "Creating deployment package..." >&2
tar -czf "$TARBALL" -C "$STAGING_DIR" .
else
echo "Error: Input must be a directory or a .tgz file" >&2
exit 1
fi
if [ "$FRAMEWORK" != "null" ]; then
echo "Detected framework: $FRAMEWORK" >&2
fi
# Deploy
echo "Deploying..." >&2
RESPONSE=$(curl -s -X POST "$DEPLOY_ENDPOINT" -F "file=@$TARBALL" -F "framework=$FRAMEWORK")
# Check for error in response
if echo "$RESPONSE" | grep -q '"error"'; then
ERROR_MSG=$(echo "$RESPONSE" | grep -o '"error":"[^"]*"' | cut -d'"' -f4)
echo "Error: $ERROR_MSG" >&2
exit 1
fi
# Extract URLs from response
PREVIEW_URL=$(echo "$RESPONSE" | grep -o '"previewUrl":"[^"]*"' | cut -d'"' -f4)
CLAIM_URL=$(echo "$RESPONSE" | grep -o '"claimUrl":"[^"]*"' | cut -d'"' -f4)
if [ -z "$PREVIEW_URL" ]; then
echo "Error: Could not extract preview URL from response" >&2
echo "$RESPONSE" >&2
exit 1
fi
echo "Deployment started. Waiting for build to complete..." >&2
echo "Preview URL: $PREVIEW_URL" >&2
# Poll the preview URL until it returns a non-5xx response (5xx = still building)
MAX_ATTEMPTS=60 # 5 minutes max (60 * 5 seconds)
ATTEMPT=0
while [ $ATTEMPT -lt $MAX_ATTEMPTS ]; do
HTTP_STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$PREVIEW_URL")
if [ "$HTTP_STATUS" -eq 200 ]; then
echo "" >&2
echo "Deployment ready!" >&2
break
elif [ "$HTTP_STATUS" -ge 500 ]; then
# 5xx means still building/deploying
echo "Building... (attempt $((ATTEMPT + 1))/$MAX_ATTEMPTS)" >&2
sleep 5
ATTEMPT=$((ATTEMPT + 1))
elif [ "$HTTP_STATUS" -ge 400 ] && [ "$HTTP_STATUS" -lt 500 ]; then
# 4xx might be an error or the app itself returns 4xx - it's responding
echo "" >&2
echo "Deployment ready (returned $HTTP_STATUS)!" >&2
break
else
# Any other status, assume it's ready
echo "" >&2
echo "Deployment ready!" >&2
break
fi
done
if [ $ATTEMPT -eq $MAX_ATTEMPTS ]; then
echo "" >&2
echo "Warning: Timed out waiting for deployment, but it may still be building." >&2
fi
echo "" >&2
echo "Preview URL: $PREVIEW_URL" >&2
echo "Claim URL: $CLAIM_URL" >&2
echo "" >&2
# Output JSON for programmatic use
echo "$RESPONSE"
Related skills
Forks & variants (3)
Deploy To Vercel has 3 known copies in the catalog totaling 200 installs. They canonicalize to this original listing.
- vercel-labs - 165 installs
- julianromli - 28 installs
- jetbrains - 7 installs
How it compares
Use deploy-to-vercel for one-command Vercel previews; use platform-specific deploy skills when the target is not Vercel.
FAQ
What frameworks does it support?
Auto-detects 40+ frameworks including Next.js, Vite, Astro, React, Vue, and more from package.json. Also handles static HTML projects.
What is a claim URL?
A claim URL transfers deployment ownership to your own Vercel account so you control the project long-term.
Is Deploy To Vercel safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.