vela-cli

Manage the complete lifecycle of your CI/CD builds and deployments with the vela-cli command-line interface.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/ryanmr/vela-skills --skill vela-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vela-cli
Source: https://github.com/ryanmr/vela-skills/tree/main/.agents/skills/vela-cli
Command: npx skills add https://github.com/ryanmr/vela-skills --skill vela-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill empowers users to manage and interact with the Vela CI/CD system directly from the command line, streamlining pipeline validation, secret management, and build operations.

Core Features & Use Cases

  • Pipeline Validation: Ensure your .vela.yml files are syntactically correct before deployment.
  • Secret Management: Securely add, view, update, and remove secrets across different scopes (repo, org, shared).
  • Build & Deployment Control: Inspect build logs, restart builds, cancel operations, and trigger deployments.
  • Use Case: Validate a new pipeline configuration locally, then add a new API key as a repository secret, and finally trigger a deployment to your staging environment.

Quick Start

Use the vela CLI to validate the pipeline in the current directory.

Frequently Asked Questions about vela-cli

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

FAQPage Schema
How do I validate a Vela CI/CD pipeline configuration locally before deployment?

You can validate Vela CI/CD pipeline configuration locally by using the CLI to check your `.vela.yml` files for syntactical correctness, ensuring they are properly formatted before triggering any deployment.

Can I manage repository and organization secrets with the Vela CLI?

Yes, the Vela CLI supports secure secret management, allowing you to add, view, update, and remove secrets across different scopes including repository, organization, and shared levels.

How do I control build lifecycles and inspect logs in Vela CI/CD?

You can control Vela CI/CD build lifecycles directly from the CLI to inspect build logs, restart failed builds, cancel ongoing operations, and trigger new deployments to your target environments.

What authentication is required to interact with the Vela CI/CD server?

Authentication is required for Vela CI/CD server communication, which you can establish by executing the `vela login` command or by configuring a local configuration file with your server credentials.

Does the Vela CLI require any external dependencies or components?

No, the Vela CLI operates without external dependencies or components, functioning entirely as a standalone command-line interface for managing your Vela CI/CD platform operations.

What is the best way to trigger a staging deployment after adding a new API key in Vela?

The best approach is to use the Vela CLI to securely add the new API key as a repository secret, validate your pipeline configuration, and then execute a command to trigger the staging deployment.