Vercel deploy

Skill yukihirop/nagi/container/skills/vercel-deploy

Deploy websites to Vercel using MCP tools. Use when the user asks to deploy, publish, or host a website.From its SKILL.md

Install

npx -y skills add yukihirop/nagi --skill vercel-deploy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 679 tokens by cl100k_base, as published. Nobody here has run it

Vercel Deploy

Deploy websites to Vercel and return the live URL.

How to use

You have these MCP tools available:

mcp__vercel__vercel_deploy — Deploy files to Vercel. Returns the deployment URL.
mcp__vercel__vercel_list_projects — List existing projects.
mcp__vercel__vercel_list_deployments — List recent deployments.
mcp__vercel__vercel_get_deployment — Get deployment details.
mcp__vercel__vercel_create_project — Create a new project.
mcp__vercel__vercel_delete_project — Delete a project.

Workflow

When the user asks you to create and deploy a website:

Build the content in memory — Compose HTML/CSS/JS as strings. Do NOT write files to disk first.
Deploy directly — Pass the strings straight to mcp__vercel__vercel_deploy:
- name: project name (lowercase, hyphens only)
- files: array of {file: "path", data: "content"} objects — data is the raw file content as a string
- projectSettings: only set when using a known framework (see below). For plain HTML/CSS/JS sites, do NOT pass projectSettings at all.
Return the URL — The deploy tool returns a URL. Share it with the user.

Important: Do NOT write files to disk and then read them back to pass to the deploy tool. This causes unnecessary read/escape loops. Build the content and pass it directly to data.

Example

For a simple static site:

mcp__vercel__vercel_deploy({
  name: "my-site",
  files: [
    { file: "index.html", data: "<html>...</html>" },
    { file: "style.css", data: "body { ... }" }
  ]
})

Critical: `projectSettings.framework` rules

The Vercel API will reject the deploy with a 400 error if projectSettings.framework is not an exact match from the allowed list. To avoid this:

Plain HTML/CSS/JS sites → Do NOT include projectSettings at all. Omit it entirely. Vercel auto-detects static sites.
Known frameworks only → Only set framework if the project actually uses one of these: nextjs, vite, astro, remix, svelte, sveltekit, nuxtjs, gatsby, vue, angular, create-react-app, solidstart, hugo, jekyll, eleventy, redwoodjs.
When in doubt → Omit projectSettings. It is always safer to let Vercel auto-detect than to guess a framework value.

Notes

Each deploy creates a unique URL. The latest deploy is also available at <project-name>.vercel.app.
If VERCEL_API_TOKEN is not set, all tools will fail with an error.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most containers cloud skills give in 679 tokens

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07

Run containers as a non-root userin 66 of 607, across 46 files
Use multi-stage buildsin 53 of 607, across 44 files
Use Promise.all for independent operationsin 47 of 607, across 13 files
Import directly instead of barrel filesin 46 of 607, across 12 files
Use ternary instead of AND for conditionalsin 45 of 607, across 12 files
Use Set or Map for O(1) lookupsin 42 of 607, across 10 files
Create a .dockerignore filein 41 of 607, across 31 files
Read individual rule files for detailsin 39 of 607, across 9 files
Copy dependency files before source codein 36 of 607, across 23 files
Authenticate server actions like API routesin 35 of 607, across 7 files
Use next/dynamic for heavy componentsin 34 of 607, across 9 files
Use React.cache for per-request deduplicationin 34 of 607, across 10 files

Said here and by no other author read

build website content in memory
pass file strings directly to deploy tool
omit projectsettings for plain sites
omit projectsettings when framework is unknown
verify api token is set

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.