Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From acedatacloud-content
Inspects Vercel projects, deployments, build logs, and domains via the Vercel REST API. Helps diagnose failed builds and trigger redeployments.
How this skill is triggered — by the user, by Claude, or both
Slash command
/acedatacloud-content:vercelWhen to use
Trigger when the user wants to list Vercel projects, list recent deployments, read a deployment's build logs to diagnose a failure, check domains, or trigger a redeploy. The connector stores a Vercel access token with the granted scope; treat env-var values as secret (never echo them) and confirm before any redeploy / mutation.
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Call the **Vercel REST API** with `curl + jq`. The user's token is in
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
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}'
# 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'
# 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.
/v1/.../env/{id} decrypt route returns secrets — don't call it unless the
user explicitly asks, and even then summarize, don't echo.state/readyState: QUEUED → BUILDING → READY | ERROR | CANCELED.created/ready are epoch ms — divide by 1000 for human time.npx claudepluginhub acedatacloud/skills --plugin acedatacloud-contentDeploys, manages, inspects, and troubleshoots Vercel projects from the CLI. Covers builds, env vars, domains, logs, metrics, Speed Insights, Core Web Vitals, firewall, cache, cron, feature flags.
Manages Vercel projects via CLI with token-based authentication, avoiding interactive login. Useful for deployments, setting environment variables, and CI/CD.
Guides Vercel CLI (vercel/vc) for deploying projects, linking repos, managing env vars/domains, viewing logs/metrics from command line. Activates on vercel commands or deployment queries.