Vercel CLI

Run bunx vercel@latest from the user's project directory, where .vercel/project.json sets the active team and project. Never install the CLI globally or through npm, npx, pnpm, or yarn. Helpers live under the skill directory:

VERCEL_SKILL_DIR="${VERCEL_SKILL_DIR:-$HOME/.agents/skills/vercel-cli}"

Explicit user instructions override anything below.

Access

VERCEL_TOKEN in the environment authenticates everything; it never appears in arguments, output, committed files, or generated .env files. bash "$VERCEL_SKILL_DIR/scripts/vercel-ensure.sh" checks Bun, the CLI, jq, curl, the token, local context, and authentication with one read-only request; run it only when the task needs live access. Missing dependencies are reported with an OS-appropriate install command, never installed automatically. vercel login and vercel open need the user's explicit request since they open a browser.

Target one-off commands with --scope <team> and explicit resource IDs. Link with vercel link --project <p> --scope <team> --yes only for repeated repository work, since it writes .vercel/project.json. Helpers resolve scope from an explicit argument, then VERCEL_TEAM_ID, VERCEL_ORG_ID, or VERCEL_PROJECT_ID, then .vercel/project.json.

What is authorized

Read-only commands (whoami, list, inspect, logs, env list, domains list, deploy --dry) run without asking. Preview deploys run when the user asked to deploy. Production deploys, promote, rollback, cache deletion, and any deletion of projects, deployments, domains, aliases, env vars, Edge Config stores, webhooks, or bypass tokens need the user's explicit intent and one unambiguous target, inspected first; when several targets are plausible, ask rather than infer. An exact user request is authorization, so add no redundant confirmation.