vercel-cli
Vercel CLI Skill
Use the installed CLI's help for command discovery, arguments, flags, defaults, and examples: start with vercel --help, then narrow to the command or subcommand. Reuse help already read for that version. These references cover decisions, dependencies, and recovery across operations.
If an older installation lacks a command or needed guidance, retain the workflow caveats and consult the matching documentation. Preserve the project's chosen CLI version; do not upgrade it merely to make a remembered command work.
Setup
Reuse the project's installed CLI and authenticated context. If the CLI is missing, follow the project's package-manager and version conventions; for a standalone installation, use npm install --global vercel. If authentication is missing, run vercel login and wait for the user to complete the login or SAML flow. In automation, use an existing VERCEL_TOKEN through the environment rather than command-line arguments.
Execution Context
- Parse stdout for URLs, structured results, and help. Recognized help exits 0; warnings and progress use stderr. JSON and streaming support vary by command.
- Non-interactive mode suppresses prompts but does not imply consent. Detected agents without a TTY can receive it automatically; plain CI may need it explicitly. Confirmation flags are command-specific. Preserve interactive-only handoffs.
- Structured errors can contain
status,reason,hint, and suggestednextcommands. Follow a suggestion only when its target and action fit the task; it does not independently authorize linking, authentication, purchases, or mutations. - Prefer first-class CLI operations when they expose the required data or mutation. For gaps, use API fallback to discover the endpoint and preserve request/response types.