Claude GitHub Copilot Skill

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.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download acedatacloud-skills-skills_vercel-c3d1703.zip · 1 KB

Install

skills CLI npx skills add https://github.com/AceDataCloud/Skills/tree/main/skills/vercel
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install acedatacloud-skills@llmmart
Git git clone https://github.com/AceDataCloud/Skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole acedatacloud/skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.
Files (skills)
  • SKILL.md 3 KB
    ---
    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.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.