vercel-deploy

Deploy projects to Vercel without authentication and return preview and claim URLs.

135|12|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Citrus-bit/medrix-flow --skill vercel-deploy-citrus-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-deploy
Source: https://github.com/Citrus-bit/medrix-flow/tree/main/skills/public/vercel-deploy-claimable
Command: npx skills add https://github.com/Citrus-bit/medrix-flow --skill vercel-deploy-citrus-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, curl, tar, and includes scripts (resource) components.

What problem does it solve?

Deploying projects to Vercel often involves repetitive setup, packaging, and URL retrieval. This skill streamlines that workflow by handling packaging, upload, and result delivery automatically.

Core Features & Use Cases

  • Packages projects as a tarball excluding node_modules and .git, detects framework from package.json, and uploads to Vercel.
  • Returns a Preview URL and a Claim URL to transfer ownership, enabling quick sharing and handoff.
  • Supports deployment from a directory or an existing tarball, making it suitable for CI/CD pipelines and quick demos.

Quick Start

Run the deploy script against your project directory to begin deployment.

Frequently Asked Questions about vercel-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an app to Vercel without manual authentication?

You can deploy to Vercel without authentication by packaging your project directory into a tarball, uploading it directly, and retrieving a preview URL alongside a claim URL to transfer project ownership later.

Can I deploy an existing tarball to Vercel instead of a directory?

Yes, deploying an existing tarball to Vercel is supported. The process accepts both a raw project directory and a pre-packaged tarball, automatically extracting and uploading the contents to generate a live preview URL.

What files are excluded when packaging a project for Vercel deployment?

When packaging a project for Vercel deployment, the system automatically excludes the node_modules and .git directories from the uploaded tarball to minimize package size and avoid uploading unnecessary dependencies or repository metadata.

Does the Vercel deployment process detect the framework automatically?

Yes, the Vercel deployment process detects the framework automatically by reading the package.json file. This ensures the correct build settings are applied to generate the preview URL without requiring manual framework configuration.

How do I transfer ownership of a Vercel preview deployment?

To transfer ownership of a Vercel preview deployment, access the claim URL returned in the JSON output alongside the previewUrl, deploymentId, and projectId. This claim URL allows you to assign the generated deployment to your own Vercel account.

Do I need curl and tar installed to deploy to Vercel from the command line?

Yes, you need curl and tar installed. These dependencies are required to package the project directory into a tarball and execute the HTTP upload to Vercel's API, which returns the JSON output containing the preview and claim URLs.