Back to Skills

vercel-deploy

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.

78,087stars10,653forksUpdated 7/29/2026

Security Assessment

Low Risk(82/100)

Detected risks:

Uploads project files to external service(The skill archives the working project directory and uploads it to a third-party deployment service, so local source code leaves the machine as part of normal operation., Deployments are created with no authentication and returned as a claimable link rather than being tied to a pre-authenticated account, which slightly widens who could take control of a deployment if the claim URL leaks.)
Security Score82/100

About vercel-deploy

Vercel Deploy is a deployment skill that packages a local project and pushes it live to Vercel, returning a preview URL plus a claimable link that lets the user transfer the deployment to their own Vercel account. Its headline convenience is that no authentication is required to run it, which solves the friction of getting a working site online quickly during a coding session ("deploy my app", "push this live", "create a preview deployment").

Operationally, the skill runs a shell script (scripts/deploy.sh) that packages the project into a tarball while excluding node_modules and .git, auto-detects the framework from package.json, uploads the package to a deployment service, and returns both the preview URL and a claim URL. Framework detection covers a broad set including Next.js, Gatsby, Remix, Nuxt, SvelteKit, Astro, Angular, Express, Hono, NestJS, Vite, and many more; static HTML projects without a package.json are handled by renaming a single non-index HTML file so it serves at the root. Results are printed for humans and also emitted as JSON (previewUrl, claimUrl, deploymentId, projectId) for programmatic use. The docs include troubleshooting for network egress restrictions on claude.ai, advising the user to allowlist Vercel domains.

The skill is aimed at developers and prototypers who want instant, low-ceremony deployments without configuring credentials up front. The main thing to understand before use is that it archives your project directory and uploads it to an external deployment service; that is the skill's intended function, but users should be aware their source is transmitted off-machine and that the resulting deployment is claimable rather than tied to a pre-authenticated account.

FAQ

How do I deploy a project?

Run the provided deploy.sh script, optionally passing a directory path or a .tgz file; it defaults to the current directory and prints a preview URL and a claim URL.

Do I need a Vercel account or API token?

No authentication is required to deploy. The claim URL lets you transfer the deployment into your own Vercel account afterward if you want to keep it.

What gets uploaded?

The script tars the project excluding node_modules and .git, then uploads that package to a deployment service. Your source files are sent to that external service as part of deploying.

What if deployment fails due to network restrictions?

The docs note this is common on claude.ai and recommend adding Vercel domains to the allowed domains in settings, then retrying.

Does it work for plain static HTML?

Yes. Projects without package.json get framework set to null, and a single non-index HTML file is renamed automatically so it serves at the site root.

All Files

2 files
scripts/deploy.sh6.7 KB
View
SKILL.md3.1 KB
View

Install vercel-deploy

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill