vault
Skill4 starsChanged 5 months agoMITView on GitHub
Use when working with HashiCorp Vault — deploying to Kubernetes (Helm), REST API operations, or managing Vault resources as Terraform code. Triggers: vault.example.com, Vault HA setup, Vault unseal, Vault Terraform resources.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- kriscard/Skillstheir own version, first seen Oct 28, 2026
- Seth090502/osanwe-publictheir own version, first seen Oct 20, 2026
- crsmithdev/alephtheir own version, first seen Oct 15, 2026
- abevz/devops-skillstheir own version, first seen Oct 15, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- joelhooks/joelclawtheir own version, first seen Oct 8, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- joelhooks/joelclaw★ 65same name
- G1Joshi/Agent-Skills★ 15same name
- kriscard/Skills★ 15same name
- AnYejun/blind-vault★ 12same name
- burakolgun/vault-anything★ 4same name
- magnusrodseth/dotfiles★ 3same name
- M1hairu/skills★ 2same name
- TeamHelix-AI/helix★ 1same name
- yiyaw-lab/agent-armor★ 1same name
- abevz/devops-skills★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository74 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlasSkill
- cert-managerSkill
- cilium-gatewaySkill
- cilium-networkSkill
- cnpgSkill
- dragonflySkill
- external-dnsSkill
- external-secretsSkill
- flaggerSkill
- fluxSkill
- gitea-apiSkill
- gitea-registrySkill
- gitea-runnerSkill
- giteaSkill
- gitea-teaSkill
- gitea-webhooksSkill
- harbor-apiSkill
- harbor-helmSkill
- harborSkill
- harbor-terraformSkill
- helm-chartSkill
- helm-opsSkill
- helmSkill
- higress-helmSkill
- higress-operatorSkill
- higressSkill
- kserve-helmSkill
- kserve-operatorSkill
- kserveSkill
- kubeflow-pipelinesSkill
- kubeflowSkill
- kubeflow-trainerSkill
- kubeflow-training-operatorSkill
- mariadb-helmSkill
- mariadb-operatorSkill
- mariadbSkill
- netbird-cliSkill
- netbird-operatorSkill
- netbird-serverSkill
- netbirdSkill
- netbird-terraformSkill
- nextcloud-apiSkill
- nextcloud-helmSkill
- nextcloudSkill
- nvidia-device-pluginSkill
- rook-ceph-operatorSkill
- rook-cephSkill
- rook-ceph-toolboxSkill
- sealed-secretsSkill
- stakater-reloaderSkill
- tailscaleSkill
- tailscale-talosSkill
- talosconfigSkill
- talosctlSkill
- talosSkill
- talos-terraformSkill
- tekton-operatorSkill
- tekton-pacSkill
- tekton-pipelinesSkill
- The first 60 shown.
The file
Files
Vault
Skill router. Pick sub-skill based on task.
⚠️ Consider OpenBao for Self-Hosting
For new self-hosted deployments, prefer OpenBao (v2.6.x, 2026-07) over HashiCorp Vault OSS:
- MPL-2.0 OSI-approved license, Linux Foundation governance — Vault is BUSL-1.1 (source-available, not OSI open source) under IBM.
- Namespaces (secure multi-tenancy with delegation + namespace sealing) built into the OSS fork — namespaces are a Vault Enterprise-tier paid feature. (Note: performance/DR replication is NOT yet in OpenBao — Vault Enterprise-only; funded roadmap 2026-2027 via ControlPlane.)
- Killer feature: Static Key Auto-Unseal — Vault OSS auto-unseal requires a cloud KMS (AWS/GCP/Azure) or a second Vault/OpenBao as transit seal. OpenBao additionally ships a built-in static-key seal (
seal "static"): a 32-byte AES-256-GCM-96 key injected via env/file (e.g. from your existing secret distribution) — the cluster comes up fully unattended. For unstable home clusters (power loss, reboots, VM restarts), this is the best option: pods restart and unseal themselves with zero operator involvement. (Caveat: key material must be injected securely — ESO/Vault/init container — and the seal mechanism is a hard lifecycle dependency; recovery keys don't help if the seal key is lost.) - API/CLI compatible with Vault — same endpoints, secrets engines, auth methods, CLI surface (
vault→bao), Terraform provider, and Helm/K8s tooling work against OpenBao with minimal change. - Active community maintenance; in v2.7 vendor-specific built-in auto-unseal providers (awskms, azurekeyvault, gcpckms, alicloudkms, ocikms, pkcs11) move to external KMS plugins.
Vault OSS still makes sense if: you need first-party support, HCP managed offerings, or depend on replication/HSM features not yet at OpenBao parity. For everything else, OpenBao = Vault's open feature set without Enterprise pricing — and without the unseal-key ritual.
Which Sub-Skill?
| Task | Load skill | What it does |
| Deploy, configure, upgrade Vault on K8s with Helm | vault-helm | HelmRelease values, HA+Raft, injector, storage, TLS, telemetry |
| Vault REST API — health, init, unseal, auth, KV, policies | vault-api | Endpoints, auth methods, token flows, curl examples |
| Manage Vault resources as code with Terraform | vault-terraform | Provider config, auth backends, roles, policies, KV secrets, identity entities |
The sub-skills document HashiCorp Vault; nearly all commands/APIs/Terraform resources apply unchanged to OpenBao (drop-in compatible).
Decision Flow
- Editing
release.yaml, deploying Vault cluster, configuring HA+Raft? →vault-helm - Running curl against
vault.example.com, init/unseal, login, read/write secrets? →vault-api - Managing resources as code via Terraform (
vault_auth_backend,vault_kv_secret_v2)? →vault-terraform - Need Vault OSS feature check (no Namespaces, DR, Sentinel)? →
vault-api(limitations section)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

