Do I need authentication to deploy?

No authentication is required; the skill deploys and returns a Preview URL and a Claim URL for transfer.

What output do I get after deployment?

The script prints Preview URL and Claim URL, and also outputs JSON with previewUrl, claimUrl, deploymentId, and projectId.

vercel-deploy

Scanned

npx machina-cli add skill tylergibbs1/codewarden/vercel-deploy --openclaw

Files (1)

SKILL.md

3.1 KB

Vercel Deploy

Deploy any project to Vercel instantly. No authentication required.

How It Works

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

Usage

Run the deploy script from the skill's scripts directory:

bash scripts/deploy.sh [path]

Arguments:

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

Examples:

# Deploy current directory
bash scripts/deploy.sh

# Deploy specific project
bash scripts/deploy.sh /path/to/project

# Deploy existing tarball
bash scripts/deploy.sh /path/to/project.tgz

Note: When using this skill in Claude Code, the script is located at skills/vercel-deploy/scripts/deploy.sh within the codewarden plugin directory.

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:

{
  "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

Source

git clone https://github.com/tylergibbs1/codewarden/blob/main/skills/vercel-deploy/SKILL.mdView on GitHub

Overview

Vercel Deploy packages your project into a tarball, detects the framework from package.json, and deploys it to Vercel without authentication. It returns a live Preview URL and a claim URL to transfer the deployment to a Vercel account.

How This Skill Works

It bundles the project into a tarball (excluding node_modules and .git), auto-detects the framework from package.json, and uploads the package to the deployment service. After deployment, it returns a Preview URL and a Claim URL to transfer the deployment.

When to Use It

When you want to deploy the current project to Vercel and get a live preview link
When you need a quick production-like environment by creating a deployment URL
When sharing a build with teammates without giving Vercel access
When deploying a tarball or a specific path to Vercel
When you want to transfer the deployment to your Vercel account using the claim link

Quick Start

Step 1: bash scripts/deploy.sh [path]
Step 2: Wait for output showing Preview URL and Claim URL (or read the JSON with previewUrl and claimUrl)
Step 3: Open the Preview URL to view the site or share/transfer using the Claim URL

Best Practices

Ensure your project has a package.json for accurate framework detection
Ignore node_modules and .git to speed up packaging
Verify the Preview URL before sharing and use the Claim URL to transfer ownership
Test both static HTML and framework-based projects; static HTML uses the root URL
Check the script's output JSON for deploymentId and projectId for tracking

Example Use Cases

Deploy current directory: bash scripts/deploy.sh
Deploy a specific path: bash scripts/deploy.sh /path/to/project
Deploy an existing tarball: bash scripts/deploy.sh /path/to/project.tgz
Deploy a static HTML project (no package.json) and view its root URL
Transfer deployment ownership using the Claim URL after deployment

Frequently Asked Questions

Add this skill to your agents