home / skills / vercel-labs / agent-skills / vercel-deploy-claimable

vercel-deploy-claimable skill

/skills/claude.ai/vercel-deploy-claimable

This skill deploys your project to Vercel instantly, returning preview and claim URLs to share or transfer.

npx playbooks add skill vercel-labs/agent-skills --skill vercel-deploy-claimable

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
3.1 KB
---
name: vercel-deploy
description: Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
metadata:
  author: vercel
  version: "1.0.0"
---

# Vercel Deploy

Deploy any project to Vercel instantly. No authentication required.

## How It Works

1. Packages your project into a tarball (excludes `node_modules` and `.git`)
2. Auto-detects framework from `package.json`
3. Uploads to deployment service
4. Returns **Preview URL** (live site) and **Claim URL** (transfer to your Vercel account)

## Usage

```bash
bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh [path]
```

**Arguments:**
- `path` - Directory to deploy, or a `.tgz` file (defaults to current directory)

**Examples:**

```bash
# Deploy current directory
bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh

# Deploy specific project
bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh /path/to/project

# Deploy existing tarball
bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh /path/to/project.tgz
```

## Output

```
Preparing deployment...
Detected framework: nextjs
Creating deployment package...
Deploying...
āœ“ Deployment successful!

Preview URL: https://skill-deploy-abc123.vercel.app
Claim URL:   https://vercel.com/claim-deployment?code=...
```

The script also outputs JSON to stdout for programmatic use:

```json
{
  "previewUrl": "https://skill-deploy-abc123.vercel.app",
  "claimUrl": "https://vercel.com/claim-deployment?code=...",
  "deploymentId": "dpl_...",
  "projectId": "prj_..."
}
```

## Framework Detection

The script auto-detects frameworks from `package.json`. Supported frameworks include:

- **React**: Next.js, Gatsby, Create React App, Remix, React Router
- **Vue**: Nuxt, Vitepress, Vuepress, Gridsome
- **Svelte**: SvelteKit, Svelte, Sapper
- **Other Frontend**: Astro, Solid Start, Angular, Ember, Preact, Docusaurus
- **Backend**: Express, Hono, Fastify, NestJS, Elysia, h3, Nitro
- **Build Tools**: Vite, Parcel
- **And more**: Blitz, Hydrogen, RedwoodJS, Storybook, Sanity, etc.

For static HTML projects (no `package.json`), framework is set to `null`.

## Static HTML Projects

For projects without a `package.json`:
- If there's a single `.html` file not named `index.html`, it gets renamed automatically
- This ensures the page is served at the root URL (`/`)

## Present Results to User

Always show both URLs:

```
āœ“ Deployment successful!

Preview URL: https://skill-deploy-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.
```

## Troubleshooting

### Network Egress Error

If deployment fails due to network restrictions (common 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 again
```

Overview

This skill deploys applications and websites to Vercel instantly and returns a live preview URL plus a claim link to transfer the deployment to your Vercel account. No authentication is required from the user; the skill packages the project, auto-detects the framework, uploads the bundle, and reports results. It works with many frontend and backend frameworks and supports static HTML projects.

How this skill works

The skill creates a tarball of the project (excluding node_modules and .git), inspects package.json to detect the framework or treats the content as static HTML, and uploads the package to the deployment service. On success it prints a human-friendly summary and emits JSON containing previewUrl, claimUrl, deploymentId, and projectId for programmatic use. It also handles simple static-site adjustments like renaming a single non-index HTML file to serve at root.

When to use it

  • Push a local project or tarball live to Vercel quickly
  • Create a preview deployment for QA or stakeholder review
  • Generate a claimable deployment to transfer into a personal or team Vercel account
  • Deploy static HTML sites without package.json
  • Obtain both a usable preview URL and a claim URL for ownership transfer

Best practices

  • Run from the project directory or pass the project path or .tgz file to the deploy script
  • Ensure package.json accurately reflects build and start scripts for correct framework detection
  • Exclude large node_modules; the script ignores node_modules automatically but keep repositories lean for faster uploads
  • Check the JSON output (previewUrl and claimUrl) for automation or CI integration
  • If network egress is blocked, add *.vercel.com to allowed domains and retry

Example use cases

  • Deploy the current project directory for a quick preview link to share with stakeholders
  • Deploy a production-ready build and get a claim URL for transferring ownership to your Vercel account
  • Create an ephemeral preview from a feature branch for QA validation
  • Upload a static HTML site where a single non-index HTML file should serve at /
  • Automate deployments in CI by consuming the JSON output (previewUrl, claimUrl, deploymentId)

FAQ

Do I need a Vercel account or token to use this skill?

No. The skill creates preview deployments and returns a claim URL so you can transfer the deployment into your Vercel account if desired.

What happens if framework detection fails?

If package.json is missing or no framework is detected the project is treated as static; for a single non-index HTML file the script will rename it to index.html so the site serves at root.

What output formats are available?

The skill prints a human-readable summary with Preview and Claim URLs and also writes JSON to stdout with previewUrl, claimUrl, deploymentId, and projectId.