vercel · acedatacloud — Claude Code skill: what it does, how to install
Inspects Vercel projects, streams build logs, and monitors deployment statuses via the Vercel REST API directly from your coding assistant.
Apache-2.0 176 installs ★ 17 updated 2026-10-25
npx skills add AceDataCloud/Skills --skill vercel -a claude-codeWhat vercel does
This skill teaches the assistant how to query the Vercel REST API using curl and jq. It fetches project lists, inspects recent deployment states, and verifies configured domains.
When a build breaks, the agent pulls logs from /v3/deployments/.../events. It isolates stdout and stderr lines to locate the stack trace. Debugging happens without opening a browser tab. Because redeploying ships changes directly to production, the agent must ask for confirmation first.
Requests rely on $VERCEL_ACCESS_TOKEN, with an optional $VERCEL_TEAM_ID parameter for team workspaces. Without a valid token scope, the API returns a 403 error. The prompt strictly forbids echoing decrypted secret environment variables into the conversation.
What it helps with
- Diagnose failed builds by inspecting raw stdout and stderr logs
- Check deployment states and preview URLs
- Verify domain configuration and DNS status
- Trigger redeployments without opening the Vercel dashboard
Example prompts for the agent
- Show the build logs for the latest failed Vercel deployment
- List recent deployments and check if my preview URL is ready
- Check verified domains for the frontend project
How to install vercel
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill vercel -a claude-code2Manually: put the files in place
~/.claude/skills/vercel/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vercel/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill vercel -a codex2Manually: put the files in place
.agents/skills/vercel/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill vercel -a cursor2Manually: put the files in place
.cursor/skills/vercel/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install AceDataCloud/Skills skills/vercel2Manually: put the files in place
.github/skills/vercel/SKILL.md1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill vercel -a gemini-cli2Platform CLI
gemini skills install https://github.com/AceDataCloud/Skills --path skills/vercelManually: put the files in place
.devin/skills/vercel/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill vercel -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vercel
How to install vercel in Claude Code?
Run npx skills add AceDataCloud/Skills --skill vercel -a claude-code in your terminal.
What does the vercel skill do?
It queries the Vercel REST API to list projects, inspect deployment states, fetch build logs, and manage domain settings using curl and jq.
How does the skill handle secrets and environment variables?
The instructions forbid printing environment variable values. It only reads metadata unless you explicitly request a summary of a specific configuration.
Source text
SKILL.md · Apache-2.0
---
name: vercel
description: 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.
when_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.
connections: [vercel]
allowed_tools: [Bash]
license: Apache-2.0
metadata:
author: acedatacloud
version: "1.0"
---
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:
```bash
TEAM=""; [ -n "$VERCEL_TEAM_ID" ] && TEAM="?teamId=$VERCEL_TEAM_ID"
AUTH="Authorization: Bearer $VERCEL_ACCESS_TOKEN"
```
## Projects & deployments
```bash
# 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
```bash
# 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
```bash
# 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.
© acedatacloud · Apache-2.0 · AceDataCloud/Skills
Similar skills
All skills for DevOps and infrastructure →vercel by other authors comes first.