Skip to content
Skills Library
DevOps & cloud · Automation

vercel-cli

/vercel-cli

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

Licence
MIT
Last repository change
07.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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

Original author description

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

How it works

  1. Auth
  2. Deploying
  3. Project Management
  4. Domains
  5. Environment Variables
  6. Common Errors
  7. Building Websites — Delegate to Frontend Engineer
  8. Best Practices
Original SKILL.md headings · 120 lines, 727 words
SKILL.md preview
---
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 CLI

You can deploy web applications to Vercel using the `vercel` CLI.

**HARD RULE: You MUST NOT write HTML, CSS, or JavaScript yourself. When asked to build a website or web app, you MUST delegate to a Frontend Engineer subagent (see "Building Websites" section below). This is not optional. Violation wastes your context window on code that belongs in a separate agent.**

## Auth

The Vercel token is injected from `.env` as the `VERCEL_TOKEN` environment variable at container spawn time. Pass `--token $VERCEL_TOKEN` on every Vercel CLI command.

Before any Vercel operation, verify auth:

```bash
vercel whoami --token $VERCEL_TOKEN
```

If this fails with an auth error, ask the user to run `/add-vercel` on the host to set up a Vercel token. Once added, retry `vercel whoami`.

## Deploying

Always use `--yes` to skip interactive prompts and `--token $VERCEL_TOKEN` for auth (OneCLI replaces with real token).

```bash
# Deploy to production
vercel deploy --yes --prod --token $VERCEL_TOKEN

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

# Preview deployment (not production)
vercel deploy --yes --token $VERCEL_TOKEN
```

After deploying, verify the live URL:

```bash
# Check deployment status
vercel inspect <deployment-url> --token $VERCEL_TOKEN
```

If you have `agent-browser` available, open the deployed URL and take a screenshot to visually verify.

## Project Management

```bash
# Link to an existing Vercel project (non-interactive)
vercel link --yes --token $VERCEL_TOKEN

# List recent deployments
vercel ls --token $VERCEL_TOKEN

# List all projects
vercel project ls --token $VERCEL_TOKEN
```

## Domains

```bash
# List domains
vercel domains ls --token $VERCEL_TOKEN

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

## Environment Variables

```bash
# Pull env vars from Vercel to local .env
vercel env pull --token $VERCEL_TOKEN

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

## Common Errors

| Error | Fix |
|-------|-----|
| `Error: No framework detected` | Ensure the project has a `package.json` with a `build` script, or set the framework in `vercel.json` |
| `Error: Rate limited` | Wait and retry. Don't loop — report to user |
| `Error: You have reached your project limit` | User needs to upgrade Vercel plan or delete unused projects |
| `ENOTFOUND api.vercel.com` | Network issue. Check proxy connectivity |
| Auth error after `vercel whoami` | Credential may be expired. Ask the user to run `/add-vercel` on the host to refresh the Vercel token |

## Building Websites — Delegate to Frontend Engineer

When asked to **build, create, or redesign** a website or web app, do NOT build it yourself. You MUST delegate to a Frontend Engineer agent. This is a two-step process and **both steps are required**:

**Step 1 — Create the agent** (skip if you already have a "frontend-engineer" destination):

```
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."
})
```

**Step 2 — Send the build request** (MANDATORY — do this immediately after step 1):

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

⚠️ **CRITICAL**: If you skip step 2, nothing happens. The agent exists but has no work. You MUST send the message. Do NOT tell the user "it's working on it" until you have actually called send_message.

After sending, tell the user you've handed it off and will share the result when it comes back. The Frontend Engineer will send you the live URL + screenshots when done — forward those to the user.

**When to delegate vs do it yourself:**
- **Delegate**: building new sites, redesigns, multi-page apps, anything that needs visual testing
- **Do yourself**: simple `vercel deploy` of an existing project, checking deployment status, managing domains/env vars

## Best Practices

- Run `pnpm run build` locally before deploying to catch build errors early
- Use `--cwd` instead of `cd` to keep your working directory stable
- For Next.js projects, `vercel deploy` auto-detects the framework — no extra config needed
- Use `vercel.json` only when you need custom build settings, rewrites, or headers

Versions

RepositoryScoreLicence
This page · mcarmona1064-cell/clawbridge-ai100MIT
vercel-labs/vercel-plugin100Apache-2.0
vercel/vercel100Apache-2.0
vercel/vercel-plugin100Apache-2.0
nanocoai/nanoclaw100MIT
mcarmona1064-cell/clawbridge-ai100MIT
420company/artemis95MIT

Database snapshot: 13.11.2026 · package version 4828933e9695 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100vercel
    Vercel CLI deploys websites, web apps and serverless functions to the Vercel platform from a terminal or CI job, and manages their environment variables, domains and logs. Use when a user asks to deploy to Vercel, create a preview deployment, ship to production, promote or roll…
  • 96vercel-deploy-ops
    Use when deploying or managing the user's Vercel.
  • 100vercel-cli-with-tokens
    Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
  • 100local-vercel-cli-806d4680
    Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, managing domains, or interacting with the Vercel platform from the command line.
  • 100vercel-cli-with-tokens
    Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
  • 100vercel-cli-with-tokens
    Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. \"deploy to vercel\", \"set up vercel\", \"add environment variables to vercel\".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.