Vercel

Inspect Vercel projects, deployments, build logs and domains via the Vercel REST API. Use when the user mentions Vercel, a deployment that failed / is building, build or runtime logs, a preview URL, project domains, or wants to check / redeploy a Vercel project.From its SKILL.md

Install

npx -y skills add AceDataCloud/Skills --skill vercel

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
13 stars13 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.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, 678 tokens by cl100k_base, as published. Nobody here has run it

Call the Vercel REST API with curl + jq. The user's token is in $VERCEL_ACCESS_TOKEN; every call needs Authorization: Bearer $VERCEL_ACCESS_TOKEN. Base URL: https://api.vercel.com. If the resource is team-scoped, append ?teamId=$VERCEL_TEAM_ID (set only when the user connected a team token).

Errors come back as {"error":{"code","message"}} — show message verbatim. 403 forbidden usually means the token can't see that team/project → re-connect with the right scope.

Helper for the optional team param:

TEAM=""; [ -n "$VERCEL_TEAM_ID" ] && TEAM="?teamId=$VERCEL_TEAM_ID"
AUTH="Authorization: Bearer $VERCEL_ACCESS_TOKEN"

Projects & deployments

# Projects
curl -sS -H "$AUTH" "https://api.vercel.com/v9/projects$TEAM" \
  | jq '.projects[] | {name, framework, latestProduction: .latestDeployments[0].url}'

# Recent deployments (optionally filter by ?projectId=… or &state=ERROR)
curl -sS -H "$AUTH" "https://api.vercel.com/v6/deployments${TEAM:-?}&limit=20" \
  | jq '.deployments[] | {uid, name, url, state, readyState, created}'

Diagnose a failed build

# Deployment detail
curl -sS -H "$AUTH" "https://api.vercel.com/v13/deployments/DEPLOYMENT_ID${TEAM:+&teamId=$VERCEL_TEAM_ID}" \
  | jq '{name, url, state: .readyState, error: .errorMessage}'

# Build / runtime events (the actual logs)
curl -sS -H "$AUTH" "https://api.vercel.com/v3/deployments/DEPLOYMENT_ID/events${TEAM:+?teamId=$VERCEL_TEAM_ID}" \
  | jq -r '.[] | select(.type=="stdout" or .type=="stderr") | .payload.text'

Domains & redeploy

# Project domains
curl -sS -H "$AUTH" "https://api.vercel.com/v9/projects/PROJECT_ID/domains${TEAM:+?teamId=$VERCEL_TEAM_ID}" \
  | jq '.domains[] | {name, verified}'

To redeploy, POST to https://api.vercel.com/v13/deployments with a deploymentId (or git source) body — confirm with the user first, it ships to production.

Gotchas

Never print env-var values. Listing project env vars returns metadata; the /v1/.../env/{id} decrypt route returns secrets — don't call it unless the user explicitly asks, and even then summarize, don't echo.
Deployment state/readyState: QUEUED → BUILDING → READY | ERROR | CANCELED.
created/ready are epoch ms — divide by 1000 for human time.

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 678 tokens

Counted across 607 of the 705 authors here whose files we hold, read 2026-09-06

Run as non-root userin 34 of 607, across 27 files
Use multi-stage buildsin 29 of 607
Set resource requests and limitsin 24 of 607, across 20 files
Configure liveness and readiness probesin 18 of 607, across 14 files
Use named volumes for persistent datain 14 of 607, across 9 files
Pin base image versionsin 14 of 607
Set up environment variablesin 14 of 607, across 10 files
Pin provider versionsin 14 of 607
Apply least privilege RBAC permissionsin 10 of 607, across 7 files
Create a dockerignore filein 10 of 607
Use remote state with lockingin 9 of 607
Pin base images by digestin 9 of 607, across 8 files

Said here and by no other author read

Call the Vercel REST API with curl and jq
Include the Authorization header with every call
Append the team parameter if team-scoped
Confirm with the user before redeploying

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.