Skip to content

Guide · Agent skill

How to use the Vercel Deploy agent skill (vercel-deploy)

Updated · written with AI from the project's own documentation and checked against our catalogue data

The vercel-deploy skill lets an AI agent put a project or website online on Vercel and return a live preview link. It is aimed at developers who want a quick shareable preview, non-technical people with a simple static page, and teams sharing a work-in-progress site. After this guide you will know what the skill does, how to install it, how to ask for a deployment in plain language, and what to check before uploading anything.

Vercel Deploybytedance/deer-flow · MIT

Quick start

  1. 1Download the skill. Download the vercel-deploy ZIP from this page.
  2. 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for all projects, or into a project's .claude/skills/ folder for one project.
  3. 3Or upload it in Claude. In the Claude apps, go to Settings, then Capabilities, then Skills, and upload the ZIP.
  4. 4Ask for a deployment. Say something like Deploy this to production or Create a preview deployment in the project folder.
  5. 5Open both links. Visit the Preview URL to see the live site. Keep the Claim URL if you want to move the deployment into your own Vercel account later.

What is an agent skill and what does vercel-deploy do?

An agent skill is a folder of instructions and scripts that an AI agent can load when a task matches it. The skill is defined by a SKILL.md file and, here, a bundled shell script.

When you ask the agent to deploy, the skill packages your project folder into a tarball, leaving out node_modules and .git. It detects the framework from package.json, uploads the package to a deployment service, and returns a Preview URL for the live site and a Claim URL that lets you transfer the deployment to your own Vercel account.

  • Preview URL: the live site you can open and share.
  • Claim URL: transfers the deployment to your Vercel account later.
  • No authentication is required to start a deployment.

How do you install the vercel-deploy skill?

Download the ZIP of the skill from this page. You can install it in one of two ways.

Option A, personal skills folder: unzip the download into ~/.claude/skills/ so the skill is available across your projects.

Option B, project skills folder: unzip the download into the .claude/skills/ folder inside a specific project so it is available only there.

Option C, Claude apps: upload the ZIP in the Claude apps under Settings, then Capabilities, then Skills.

  • The skill folder should contain scripts/deploy.sh and SKILL.md.
  • The agent needs a bash shell available to run the script.

How do you trigger the skill with a natural request?

You do not need to type a command. The skill is meant to be triggered by plain requests about deployment. The skill's description lists examples such as the phrases below, and the agent should load it when your request matches this kind of action.

Say what you want to happen and, if useful, ask for the link back in the same message. Mentioning the project folder helps when you are not working in it.

  • Deploy my app
  • Deploy this to production
  • Create a preview deployment
  • Deploy and give me the link
  • Push this live

Can you run the deploy script yourself?

The agent normally runs the script for you, but the skill's SKILL.md shows the underlying command. The path argument is optional. If you leave it out, the current directory is deployed. You can also point it at a project folder or an existing .tgz file.

Run it from a terminal only if you understand what will be uploaded. The output includes the Preview URL and Claim URL, and the script also prints JSON with previewUrl, claimUrl, deploymentId and projectId for programmatic use.

  • path: a directory to deploy, or a .tgz file. Defaults to the current directory.
bash /mnt/skills/public/vercel-deploy/scripts/deploy.sh /path/to/project

What happens with framework detection and static HTML?

The script reads package.json to detect frameworks. The source lists support for many, including React-based tools such as Next.js, Gatsby and Remix, Vue-based tools such as Nuxt and Vitepress, Svelte-based tools such as SvelteKit, and backend frameworks such as Express and Hono, plus build tools such as Vite and Parcel.

Projects without a package.json are treated as static HTML and the framework is set to null. If there is a single .html file not named index.html, the script renames it so the page is served at the root URL.

What should you check before deploying?

Anything in the project folder is uploaded to a third-party service, and the resulting site is publicly reachable by its URL. Do not deploy projects that contain secrets, API keys, or private data. The skill also does not offer controlled environments, custom domains or audited deploys, so it is not a fit for production systems that need those.

The skill needs network access to its deploy endpoint and to Vercel. If the agent reports a network restriction, for example on claude.ai, the source says to add *.vercel.com to the allowed domains in the Capabilities settings and try again.

  • Remove .env files and secrets before asking for a deploy.
  • Check that the Claim URL is shared only with people who should own the site.
  • Expect the script to run on your machine or the agent's environment, so review scripts/deploy.sh if you need to.

What people use it for

  • Sharing a finished web app with a client as a preview link.
  • Putting a simple static HTML page online without setting up hosting.
  • Showing a work-in-progress site to a reviewer or teammate.
  • Getting a quick live URL for a Vite, Astro or Next.js project to test in a browser.

Frequently asked questions

Is the vercel-deploy skill free to use?

The source does not state pricing. It says no API key or account is required for the initial deploy, and a Vercel account is needed only to claim the deployment. The skill is published under the MIT licence.

Do I need a Vercel account to use it?

No. The initial deploy needs no authentication and returns a Preview URL and a Claim URL. You only need a Vercel account if you want to claim the deployment and transfer it to your account.

What does the skill require to run?

It needs a bash shell available to the agent and network access to the skill's deploy endpoint and to Vercel. The skill runs scripts and uses the network.

How do I install vercel-deploy in Claude?

Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. Alternatively, upload the ZIP in the Claude apps under Settings, then Capabilities, then Skills.

Why does deployment fail with a network restriction error?

The source says this is common on claude.ai. Go to claude.ai/settings/capabilities, add *.vercel.com to the allowed domains, and try deploying again.

Is it safe to deploy projects with secrets using this skill?

Not according to the source. The project folder is uploaded to a third-party service and the site is publicly reachable by its URL, so projects with secrets or private data should not be deployed with it.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use vercel-deploy when you want a fast, shareable live link for a finished or simple project, and you are comfortable with a public URL and no account at the start. Pick another hosting route if the project contains secrets or private data, or if you need controlled environments, custom domains or audited deploys.

Download the skill