vault-user
starsforks
How to install vault-user?
mvschwarz/openrig/vault-user
$npx -y skills add mvschwarz/openrig --skill vault-userYou have access to a HashiCorp Vault instance managed by this rig's environment.
SKILL.md
| 1 | # Vault User |
| 2 | |
| 3 | You have access to a HashiCorp Vault instance managed by this rig's environment. |
| 4 | |
| 5 | ## Connection |
| 6 | |
| 7 | - **Address:** `http://127.0.0.1:8200` |
| 8 | - **Token:** `openrig-dev-token` |
| 9 | - **Auth header:** `X-Vault-Token: openrig-dev-token` |
| 10 | |
| 11 | Always set the token before making API calls. For curl, use `-H "X-Vault-Token: openrig-dev-token"`. |
| 12 | |
| 13 | ## Health Check |
| 14 | |
| 15 | ```bash |
| 16 | curl -s http://127.0.0.1:8200/v1/sys/health | jq . |
| 17 | ``` |
| 18 | |
| 19 | A healthy response has `"initialized": true` and `"sealed": false`. |
| 20 | |
| 21 | ## Secret Operations |
| 22 | |
| 23 | ### Write a secret |
| 24 | |
| 25 | ```bash |
| 26 | curl -s -X POST http://127.0.0.1:8200/v1/secret/data/<path> \ |
| 27 | -H "X-Vault-Token: openrig-dev-token" \ |
| 28 | -d '{"data": {"key": "value"}}' | jq . |
| 29 | ``` |
| 30 | |
| 31 | ### Read a secret |
| 32 | |
| 33 | ```bash |
| 34 | curl -s http://127.0.0.1:8200/v1/secret/data/<path> \ |
| 35 | -H "X-Vault-Token: openrig-dev-token" | jq . |
| 36 | ``` |
| 37 | |
| 38 | The secret value is in `.data.data`. |
| 39 | |
| 40 | ### List secrets |
| 41 | |
| 42 | ```bash |
| 43 | curl -s -X LIST http://127.0.0.1:8200/v1/secret/metadata/ \ |
| 44 | -H "X-Vault-Token: openrig-dev-token" | jq . |
| 45 | ``` |
| 46 | |
| 47 | List a subdirectory by appending the path: `.../secret/metadata/<prefix>/`. |
| 48 | |
| 49 | ### Delete a secret |
| 50 | |
| 51 | ```bash |
| 52 | curl -s -X DELETE http://127.0.0.1:8200/v1/secret/data/<path> \ |
| 53 | -H "X-Vault-Token: openrig-dev-token" |
| 54 | ``` |
| 55 | |
| 56 | ## Explaining Secrets |
| 57 | |
| 58 | When asked to explain the current secret structure, list all paths and summarize what each contains. Use the list endpoint recursively if needed. |
| 59 | |
| 60 | ## Important Notes |
| 61 | |
| 62 | - This is Vault dev mode — all data is in-memory and lost on restart |
| 63 | - The KV secrets engine is mounted at `secret/` by default in dev mode |
| 64 | - Use the `rig env status` command to verify Vault health through OpenRig before direct probing |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
