vercel-deploy

Deploy static websites and web applications to Vercel non-interactively.

9|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/llm011/ethan-agent --skill vercel-deploy-llm011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-deploy
Source: https://github.com/llm011/ethan-agent/tree/main/ethan/defaults/skills/vercel-deploy
Command: npx skills add https://github.com/llm011/ethan-agent --skill vercel-deploy-llm011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the secure, non-interactive deployment of static websites and web applications to Vercel while reducing project-management overhead and protecting deployment credentials.

Core Features & Use Cases

  • Secure Credential Handling: Loads Vercel credentials from the recommended Ethan secret locations without exposing token values.
  • Host Project Deployment: Organizes web tools under a shared host project and deploys them using the Vercel CLI.
  • Build and Publish Workflows: Supports standard projects and pnpm applications, including production builds and deployment of generated artifacts.
  • Use Case: Deploy a newly created web tool to Vercel, reuse the shared host project when appropriate, and return the resulting vercel.app URL.

Quick Start

Ask the Vercel deploy skill to publish the current web application to production and return its live URL.

Frequently Asked Questions about vercel-deploy

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

FAQPage Schema
How do I deploy a web application to Vercel non-interactively?

Deploy a web application to Vercel non-interactively by loading a Vercel access token from secure secret locations and executing the Vercel CLI with absolute deployment paths. This returns a live vercel.app URL without manual prompts.

How do I deploy a pnpm project to production hosting on Vercel?

Deploy a pnpm project to production hosting on Vercel by applying appropriate Vercel CLI build configurations. The workflow executes the production build and deploys the generated artifacts directly to the host environment.

Do I need a Vercel access token to publish static websites?

Yes, a Vercel access token is required to publish static websites securely. The deployment process loads credentials from recommended secret locations without exposing token values during the build and publish workflow.

What's the best way to manage multiple web tools under a shared Vercel project?

Manage multiple web tools under a shared Vercel project by organizing them within a host project structure. This approach reduces project-management overhead while deploying each tool independently using the Vercel CLI.

Does this Vercel deployment approach work with built output from standard projects?

Yes, this Vercel deployment approach works with built output from standard projects. It supports deploying generated artifacts and static websites by applying appropriate Vercel CLI build and project configurations.

Why does my Vercel deployment fail when using relative paths?

Vercel deployment fails with relative paths because the process requires absolute deployment paths. Providing correct absolute paths for your web application ensures the Vercel CLI can locate and upload build artifacts successfully.