vercel-clilisted

Operate Vercel from a coding-agent terminal with the official Vercel CLI and bundled REST helpers. Use when the agent needs to inspect or manage Vercel teams, projects, deployments, build or runtime logs, environment variables, domains, aliases, Edge Config stores, webhooks, deployment-protection bypass tokens, log drains, promotions, rollbacks, or redeployments; when the user asks to deploy to Vercel, diagnose a Vercel deployment, check Vercel logs, manage Vercel environment variables, or invoke vercel-cli; or when translating a Vercel MCP workflow to shell commands. Do not use for authoring application code that merely runs on Vercel, application runtime integration through @vercel/sdk, continuous monitoring, or Vercel MCP server configuration.
arthjean/skills · ★ 3 · AI & Automation · score 66

Install: claude install-skill arthjean/skills

# Vercel CLI Operate Vercel through `bunx vercel@latest` and the bundled shell helpers. Keep the working directory in the user's project so Vercel can resolve its local `.vercel` context. ## Operating contract 1. Set the absolute directory containing this `SKILL.md` as `VERCEL_SKILL_DIR`. In a standard user installation: ```bash VERCEL_SKILL_DIR="${VERCEL_SKILL_DIR:-$HOME/.agents/skills/vercel-cli}" ``` 2. Do not `cd` into the skill directory before running Vercel commands. The current project directory determines the active `.vercel/project.json` context. 3. Use `bunx vercel@latest`. Do not install Vercel CLI globally and do not use npm, npx, pnpm, or yarn. 4. Authenticate with `VERCEL_TOKEN` in the environment. Do not place the token in command arguments, output, committed files, or generated `.env` files. 5. Prefer native Vercel CLI commands. Use bundled helpers for structured deployment output, REST-only operations, or non-interactive bulk operations. 6. Keep browser use opt-in. Do not run `vercel login` or `vercel open` unless the user explicitly requested browser authentication or dashboard navigation. 7. Require explicit destructive intent and an unambiguous target before deleting projects, deployments, domains, aliases, environment variables, Edge Config stores, webhooks, or bypass tokens. Apply the same rule to production deploys, promotion, rollback, cache deletion, and domain purchase or transfer. 8. Inspect the current target before a production muta