hashicorp-vault

Configure Vault engines, auth methods, and policies for secret management.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill hashicorp-vault-toanpv90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hashicorp-vault
Source: https://github.com/ToanPV90/dotfiles/tree/main/agents/.agents/skills/hashicorp-vault
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill hashicorp-vault-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

HashiCorp Vault solves the problem of securely storing and distributing sensitive data (like credentials and encryption keys) without hardcoding secrets into applications or configuration files.

Core Features & Use Cases

  • Centralized secrets management: Organize secrets via KV engines with versioning, listing, and controlled access.
  • Dynamic credentials & automation: Generate short-lived database and cloud credentials on demand.
  • PKI certificate authority: Issue and manage TLS certificates and certificate lifecycles through a PKI engine.
  • Authentication & authorization: Integrate with common auth methods (AppRole, Kubernetes, OIDC) and enforce policies with least privilege.
  • Application integration: Use SDKs (e.g., Python hvac) or Kubernetes Vault Agent patterns to fetch secrets at runtime.

Quick Start

Initialize and unseal a dev Vault, then write and read a KV v2 secret using the Vault CLI.

Frequently Asked Questions about hashicorp-vault

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

FAQPage Schema
How do I manage dynamic database credentials instead of using static passwords?

Centralized secrets management uses a Key-Value (KV) secrets engine with versioning to store and organize sensitive data, allowing controlled read and write access while preventing hardcoded secrets in application configurations.

Can I use Kubernetes authentication to let pods fetch secrets securely?

A PKI certificate authority issues and manages TLS certificates by enabling a PKI secrets engine, configuring root and intermediate CAs, and defining roles to automate certificate generation and lifecycle for applications.

What's the best way to enforce least-privilege access for applications fetching secrets?

Least-privilege access is enforced by writing HCL-defined Vault policies that restrict capabilities on specific secret paths, then attaching those policies to authenticated identities like AppRole or Kubernetes auth backends.

Does configuring Vault for PKI and dynamic cloud credentials require specific CLI tools?

Configuring Vault engines for PKI and dynamic cloud credentials requires the Vault CLI for HCL configuration and engine enablement, and requires the jq dependency to parse JSON outputs during authenticated secret retrieval.