VE

vercel-deploy-claimable

Deploys projects to Vercel from your local directory, providing instant preview and claim URLs.

Install

mkdir -p .claude/skills/vercel-deploy-claimable-t-sunm && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13873" && unzip -o skill.zip -d .claude/skills/vercel-deploy-claimable-t-sunm && rm skill.zip

Installs to .claude/skills/vercel-deploy-claimable-t-sunm

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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...
200 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Package projects for deployment
  • Auto-detect framework from `package.json`
  • Upload projects to Vercel deployment service
  • Return live preview URLs
  • Return claimable production URLs
  • Handle static HTML projects without `package.json`

How it works

The skill packages the project, detects its framework, uploads it to Vercel, and then provides a preview URL and a claim URL for the deployment.

Inputs & outputs

You give it
Project directory or .tgz file
You get back
Preview URL and Claim URL for the Vercel deployment

When to use vercel-deploy-claimable

  • Deploy app to production
  • Create a preview deployment
  • Push local project to Vercel

About this skill

Vercel Deploy

Deploy any project to Vercel instantly. No authentication required.

When to Use This Skill

Use this skill when:

  • User requests deployment actions like "Deploy my app"
  • Deploying to production
  • Creating preview deployments
  • User asks for deployment links
  • Pushing projects live to Vercel

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 /mnt/skills/user/vercel-deploy/scripts/deploy.sh [path]

Arguments:

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

Examples:

# 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:

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

When not to use it

  • When network egress is restricted for *.vercel.com

Limitations

  • Deployment may fail due to network restrictions if *.vercel.com is not allowed.
  • The skill excludes `node_modules` and `.git` from the tarball.
  • For static HTML projects, a single .html file not named `index.html` gets renamed automatically.

How it compares

This skill automates the Vercel deployment process, including framework detection and providing claimable URLs, which is more simplify than manual deployment steps.

Compared to similar skills

vercel-deploy-claimable side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
vercel-deploy-claimable (this skill)05moReviewBeginner
gcp-cloud-run55moReviewIntermediate
flow-nexus-platform64moReviewBeginner
smithery-mcp-deployment88moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

gcp-cloud-run

aj-geddes

Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.

5107

flow-nexus-platform

ruvnet

Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges

691

smithery-mcp-deployment

CaullenOmdahl

Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment

881

deployment-pipeline-design

wshobson

Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.

670

vercel-deployment

davila7

Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.

359

netlify-deploy

openai

Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.

740

Search skills

Search the agent skills registry