vercel

SkillCloud & infra

Use the vercel_deploy core tool to manage Vercel projects, domains, and deployment listings from Argent runtime.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the vercel skill

What this skill tells your AI

The instructions your AI receives, as published by argentaios/argentos-core in skills/vercel/SKILL.md and read by ahel’s review.

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.

Signals

GitHub stars
126
Forks
22
Last commit
Jul 2026
Hacker News mentions
20
Advanced
Catalog kind
skill
Gateway key
vercel
Source
github.com/argentaios/argentos-core