vercel-cli-usage

Manage Vercel deployments via CLI with token authentication.

Updated Mar 28, 2025

Search Tags:#automation #logs #cli #vercel #deployments #env-vars #project-info

Ready to run

npx skills add https://github.com/gileck/app-template-ai --skill vercel-cli-usage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vercel-cli-usage
Source: https://github.com/gileck/app-template-ai/tree/main/.ai/skills/template/vercel-cli-usage
Command: npx skills add https://github.com/gileck/app-template-ai --skill vercel-cli-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill enables automated management of Vercel deployments through the Vercel CLI, reducing manual context switching and speeding up deployment workflows.

Core Features & Use Cases

List Deployments: Retrieve recent deployments across production and preview targets.
Get Deployment Info & Logs: Inspect deployment details and fetch build logs for faster debugging.
Environment Management: View and push environment variables to all targets to ensure consistent runtime configuration.
Project Insights: Show current project details and status to monitor health and progress.
Use Case: When maintaining multiple apps on Vercel, use the CLI to automate routine checks, report statuses, and align deployments with release cycles.

Quick Start

Install and authenticate

Ensure VERCEL_TOKEN is set in .env
Optionally run vercel link to wire the project for auto-detection

Common commands

List deployments: yarn vercel-cli list
Deployment info: yarn vercel-cli info --deployment dpl_xxxx
Build logs: yarn vercel-cli logs --deployment dpl_xxxx
Environment vars: yarn vercel-cli env
Push env vars: yarn vercel-cli env:push
Show project: yarn vercel-cli project

Frequently Asked Questions about vercel-cli-usage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Vercel deployments using the CLI?▼

Automate Vercel deployments via the CLI by configuring a VERCEL_TOKEN environment variable and using script commands to list deployments, inspect project info, and fetch build logs programmatically across production and preview targets.

How do I fetch Vercel build logs for a specific deployment?▼

Fetch Vercel build logs by running the CLI logs command with the specific deployment ID, such as passing the dpl_xxxx identifier. This retrieves detailed build output for faster debugging of failed or stalled deployments directly from the terminal.

Can I manage Vercel environment variables across multiple deployment targets?▼

Yes, you can manage Vercel environment variables across multiple targets by viewing existing vars and pushing new ones to production and preview environments. This ensures consistent runtime configuration across all Vercel deployment targets without manual dashboard configuration.

What do I need to set up before using Vercel CLI for deployment management?▼

Before using the Vercel CLI for deployment management, you need a VERCEL_TOKEN set in your environment and optionally execute vercel link to wire your project for auto-detection. You can also configure project-id and team-id options to target specific Vercel resources.

How do I list recent Vercel deployments for production and preview targets?▼

List recent Vercel deployments across production and preview targets by running the list command provided by the CLI. This retrieves recent deployment records programmatically, allowing you to monitor project health and report statuses without accessing the web dashboard.