vault-cli

Manage Vault secrets via CLI or REST API with authentication and policy controls.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/BjzyLabs/vCenterCert --skill vault-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-cli
Source: https://github.com/BjzyLabs/vCenterCert/tree/main/.ruler/skills/vault-cli
Command: npx skills add https://github.com/BjzyLabs/vCenterCert --skill vault-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables secure Vault secrets management from the command line, preventing secret leakage and manual credential handling in automation workflows.

Core Features & Use Cases

  • Secure Access: Retrieve, rotate, and encrypt secrets using the Vault CLI or REST API.
  • Authentication & Policy: Manage token/AppRole-based authentication and access-control policies.
  • Use Case: Automate credentials retrieval in CI/CD pipelines without exposing secrets in code or logs.

Quick Start

Authenticate with Vault and perform common secret operations:

  • vault token lookup
  • vault kv get -field=username kvProd_v2/AWX/Application-Prod
  • vault kv get -field=token kvProd_v2/AWX/Application-Prod
  • curl -H "X-API-KEY: $(vault kv get -field=token kvProd_v2/AWX/Application-Prod)" https://keep-api.bjzy.me

Frequently Asked Questions about vault-cli

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

FAQPage Schema
How do I retrieve Vault secrets via the command line without exposing them in logs?

You can retrieve Vault secrets via the command line using 'vault kv get -field=[value] [path]', which extracts specific fields safely and prevents secret leakage in automation logs.

Can I use the Vault CLI for token and AppRole authentication in production environments?

Yes, the Vault CLI supports token and AppRole-based authentication, enabling you to manage access-control policies and securely interact with production Vault instances via the command line or REST API.

What's the best way to automate secret rotation and encryption across development environments?

The best way to automate secret rotation and encryption is using vault CLI commands within operational workflows, applying consistent policy administration safeguards across both development and production environments.

How does the Vault REST API integrate with CLI commands for CI/CD pipeline credential retrieval?

The Vault REST API integrates with CLI commands by using the CLI to fetch secrets dynamically, such as using 'vault kv get' to supply an X-API-KEY header for curl requests in CI/CD pipelines.

Do I need a specific policy to prevent secret leakage when running vault CLI commands?

You need to configure proper access-control policies and use targeted field retrieval with the vault CLI to prevent secret leakage, ensuring credentials are not exposed in code or automation logs.