home / skills / derklinke / codex-config / vercel-deploy

vercel-deploy skill

needs review

/skills/vercel-deploy

This skill deploys your project to Vercel instantly, returning preview and claim URLs for quick sharing and transfer.

npx playbooks add skill derklinke/codex-config --skill vercel-deploy

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.
---

# 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/admin-settings/capabilities
2. Add *.vercel.com to the allowed domains
3. Try deploying again
```

Overview

This skill deploys applications and websites to Vercel quickly and without requiring authentication. It packages your project, auto-detects the framework, uploads the build, and returns a live preview URL plus a claimable link to transfer the deployment to your Vercel account. Ideal for quick previews, testing pull-request branches, or pushing a site live from a local directory or tarball.

How this skill works

The script creates a tarball of the target directory (excluding node_modules and .git), reads package.json to auto-detect framework and build settings, and uploads the bundle to a deployment service. After deployment it prints a human-readable summary and emits JSON containing previewUrl, claimUrl, deploymentId, and projectId for programmatic integration. No Vercel auth is required — the claim URL lets you attach the deployment to your account.

When to use it

Create a preview deployment for a feature branch or PR
Quickly publish a static site or frontend project from a local folder
Deploy a backend or server-rendered app for testing
Push a production-ready site live and get a claim link to transfer ownership
Integrate into CI to produce preview URLs for every commit

Best practices

Exclude large dependencies (node_modules) and unnecessary build artifacts before deploying
Ensure package.json accurately lists frameworks/build scripts for correct detection
Use the preview URL for sharing and QA, and use the claim URL to move the deployment into your Vercel account
Supply a path to a prebuilt .tgz when deploying from CI to skip packaging step
Check the JSON output for programmatic workflows and automation

Example use cases

Deploy current directory quickly: bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh
Deploy a specific project folder: bash .../deploy.sh /path/to/project
Deploy an existing tarball from CI: bash .../deploy.sh /path/to/project.tgz
Generate preview URLs for PRs so reviewers can view the live site
Publish a static HTML project without package.json — script will handle index renaming if needed

FAQ

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

No. The skill creates a preview deployment and returns a claim URL you can use to attach the deployment to your Vercel account.

What frameworks are supported for auto-detection?

Many frontend and backend frameworks are supported (Next.js, React, Vue, Svelte, Astro, Express, NestJS, Vite, Parcel, etc.). If no package.json exists, the skill treats the project as static HTML.

What if deployment fails due to network restrictions?

Deployment can fail if egress to Vercel is blocked. Allow *.vercel.com in your network or platform settings, then retry. The script will report the specific network error.