| name | vercel-status |
| description | Check Vercel deployment status, recent deployments, and domains for the public site via the Vercel REST API. Use when asked about the website, site status, or Vercel deployments. |
Vercel Status
Queries the Vercel REST API (https://api.vercel.com) directly — does not shell out
to the vercel CLI. This keeps the skill runnable from any environment that has
curl + python, without needing the CLI installed in the openclaw container.
The projectId, orgId (team), and projectName are read from .vercel/project.json
at repo root (created by vercel link) at runtime — the script reads them itself, so
they are not duplicated here.
Auth is via VERCEL_TOKEN env var, passed as Authorization: Bearer $VERCEL_TOKEN.
Generate at https://vercel.com/account/settings/tokens. If the token is missing the
skill fails loud — per the "no silent defaults" rule, it will not fall back to
anonymous calls.
Usage
scripts/run.sh
scripts/run.sh deployments [n]
scripts/run.sh production
scripts/run.sh domains
Endpoints used
GET /v6/deployments?projectId=...&teamId=...&limit=N — list recent deployments
GET /v6/deployments?projectId=...&teamId=...&target=production&limit=1 — latest prod
GET /v9/projects/{projectId}/domains?teamId=... — project domains
Output
For each deployment: url, state (READY / BUILDING / ERROR / CANCELED), target
(production / preview), createdAt, git commit SHA if present. Domains show the
hostname and verification state.