Vercel CLI

What it does

When your agent uses it

• Asked to deploy
• Publish a web application
• Manage Vercel projects
• Environment variables

Example prompts

• “/vercel-cli”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

1. 1Local build passes — run npm run build (or the project's build command) before vercel deploy. If the build fails locally, fix it first…
2. 2Deployment succeeded — the vercel deploy output shows a "Production: https://..." URL and the status is READY (confirm with vercel inspect).
3. 3Live URL responds — curl -sI | head -1 should return HTTP/2 200 (or another 2xx/3xx). A 404/500 means something's broken even though…
4. 4Optional visual check — if agent-browser is loaded, open the URL and eyeball it. Helpful for catching broken layouts that a 200 response…

What it can do on your machine

Read from SKILL.md and the folder at commit 66f0823. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • vercel
  • npm
  • curl
  • pnpm

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • vercel.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vercel CLI loads about 1.4k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 622 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~40

When it runs · the whole SKILL.md, loaded when a task matches

~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:83

  # Pull env vars from Vercel to local .env

• WarningContains instruction-override wording (e.g. “without asking the user”)SKILL.md:119

  has no work. You MUST send the message. Do NOT tell the user "it's working on it" until you have actually called send_me

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nanocoai/nanoclaw at commit 66f0823, republished under its MIT licence (© nanocoai). 622 words, ~1,444 tokens.

name

vercel-cli

description

Deploy apps to Vercel. Use when asked to deploy, ship, or publish a web application, or manage Vercel projects, domains, and environment variables.

vercel whoami --token placeholder

# Deploy to production
vercel deploy --yes --prod --token placeholder

# Deploy from a specific directory
vercel deploy --yes --prod --token placeholder --cwd /path/to/project

# Preview deployment (not production)
vercel deploy --yes --token placeholder

# Check deployment status
vercel inspect <deployment-url> --token placeholder

# Link to an existing Vercel project (non-interactive)
vercel link --yes --token placeholder

# List recent deployments
vercel ls --token placeholder

# List all projects
vercel project ls --token placeholder

# List domains
vercel domains ls --token placeholder

# Add a domain to the current project
vercel domains add example.com --token placeholder

# Pull env vars from Vercel to local .env
vercel env pull --token placeholder

# Add an env var (use echo to pipe the value — avoids interactive prompt)
echo "value" | vercel env add VAR_NAME production --token placeholder

create_agent({
  name: "Frontend Engineer",
  instructions: "You are a dedicated frontend engineer. Your frontend-engineer skill has your full workflow. Build what is requested, test it visually with agent-browser, deploy to Vercel, and send back the live URL + screenshots to your parent agent when done."
})

send_message(to: "frontend-engineer", text: "<full description of what to build, including design requirements, content, colors, and any assets>")

© nanocoai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/add-vercel/container-skills/vercel-cli of nanocoai/nanoclaw.

Open the folder on GitHubat commit 66f0823