# Vercel > Query Vercel deployments, build logs, runtime logs, and deployment status through the Vercel CLI. Use when users ask to debug Vercel deployments, inspect failed builds, fetch production or preview runtime logs, find a deployment for a project or commit SHA, or investigate Vercel-hosted app errors. Do not use it for deploying, rolling back, changing project settings, domains, env vars, caches, storage, or any other Vercel mutation. - Skill: `getsentry/vercel` (Agent Skill) - Install (CLI): `npx skillmds@latest add getsentry/vercel` - Raw SKILL.md: https://api.skillmd.com/api/skills/getsentry/vercel/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: Sentry (https://skillmd.com/u/getsentry) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/getsentry/vercel --- # Vercel Operations Use this skill for read-only Vercel deployment and log investigations. ## Read-only command allowlist Run only these Vercel CLI commands: - `vercel logs` - `vercel inspect` - `vercel list` or `vercel ls` - `vercel help`, `vercel --help`, or `vercel --help` Do not run `deploy`, `rollback`, `promote`, `remove`, `env`, `alias`, `dns`, `project`, `cache`, `blob`, `certs`, `teams`, `domains`, `git`, `link`, `login`, `logout`, `switch`, `pull`, `build`, `dev`, `redeploy`, `bisect`, `api`, or any command that creates, updates, deletes, purges, promotes, deploys, links, authenticates, or changes Vercel state. ## Workflow 1. Resolve the target: - Determine whether the user needs runtime logs, build logs, deployment status, or deployment discovery. - Prefer explicit deployment IDs, deployment URLs, project names, environments, branch names, commit SHAs, status filters, and time windows from the user. - When the user did not specify a project or team, read `vercel.project` and `vercel.team` with `jr-rpc config get` and treat them as optional conversation defaults. Explicit user input always wins. - Only set or change `vercel.project` and `vercel.team` when the user explicitly asks to store a default for this conversation or channel. - Ask one concise follow-up only when the request cannot be bounded to a project, deployment, commit, or time window from the thread or config. 2. Run the narrowest safe command: - The runtime provides Vercel authentication. Do not set, print, echo, write, or ask for `JUNIOR_VERCEL_TOKEN` or `VERCEL_TOKEN`. - If a command shape or flag is unclear, inspect `vercel --help` before guessing. - Add `--scope ` when a team is known. - Add `--project ` when a project is known and the command supports it. - For runtime logs, prefer `vercel logs --project --since --limit 20 --json` plus user-provided filters such as `--environment`, `--level`, `--status-code`, `--source`, `--query`, or `--deployment`. - Use `vercel inspect --logs` for build logs. Add `--wait` only when the user explicitly wants to wait for an active build; also bound it with `--timeout`. - Use `vercel list ` or `vercel ls ` to find deployments. Prefer filters such as `--status`, `--environment`, `--prod`, or `--meta githubCommitSha=` when available. - For a deployment watch or event task, call the `vercel_deployment` plugin tool with the project name and optional team slug or ID. Omit `commitSha` to watch every deployment for the project; add `target` (`production`, `preview`, or `staging`) to limit the watch to one environment; add a full 40-character `commitSha` to watch one deployment (`target` defaults to `production` when omitted with a commit). The tool resolves the canonical project ID through Vercel before Junior creates the conversation subscription or event task. - Use `--follow` only when the user asks for live logs, and stop once enough evidence is captured. Do not leave a streaming command running indefinitely. 3. Bound and minimize output: - Always use a time window for log searches. Default to the last hour for "right now" incidents and the last 24 hours for retrospective deployment investigations. - Prefer JSON output for `vercel logs` when parsing or summarizing. - Keep page sizes small. Start with 20 log lines or fewer unless the user asked for more. - Quote only the minimum log text needed as evidence. Vercel logs may contain customer data, secrets, request headers, or other sensitive payloads. 4. Report the result: - Answer the user first with deployment status, error pattern, top failing route/function, or the absence of matching logs. - Include the project, environment, deployment, time window, and filters used. - Include Vercel deployment or dashboard URLs when the CLI output provides them. Do not fabricate URLs from incomplete IDs. ## Failure handling - Missing `JUNIOR_VERCEL_TOKEN`: tell the operator to add `JUNIOR_VERCEL_TOKEN` to the Junior deployment environment and redeploy. - `401`, invalid token, expired token, or revoked token: report that the configured Vercel token cannot authenticate. - `403` or permission denied: report that the configured Vercel token or service account cannot read the requested project/deployment/logs. Do not guess missing Vercel permission scopes. - Project not found: confirm `vercel.project`, `vercel.team`, and the user-provided project name or scope. - Rate limiting or transient network failure: retry the same bounded read command once. If it still fails, report the throttle or network failure and stop. - Mutation request: decline briefly and explain this skill is limited to read-only Vercel logs, deployment inspection, and deployment listing.