mvschwarz/openrig / packages/daemon/specs/agents/apps/vault-specialist/skills/vault-user
vault-user
VerifiedUse when checking the health of this rig's HashiCorp Vault or writing, reading, listing, deleting or explaining its secrets.
Vault User
You have access to a HashiCorp Vault instance managed by this rig's environment.
Connection
- Address:
http://127.0.0.1:8200 - Token:
openrig-dev-token - Auth header:
X-Vault-Token: openrig-dev-token
Always set the token before making API calls. For curl, use -H "X-Vault-Token: openrig-dev-token".
Health Check
curl -s http://127.0.0.1:8200/v1/sys/health | jq .
A healthy response has "initialized": true and "sealed": false.
Secret Operations
Write a secret
curl -s -X POST http://127.0.0.1:8200/v1/secret/data/<path> \
-H "X-Vault-Token: openrig-dev-token" \
-d '{"data": {"key": "value"}}' | jq .
Read a secret
curl -s http://127.0.0.1:8200/v1/secret/data/<path> \
-H "X-Vault-Token: openrig-dev-token" | jq .
The secret value is in .data.data.
List secrets
curl -s -X LIST http://127.0.0.1:8200/v1/secret/metadata/ \
-H "X-Vault-Token: openrig-dev-token" | jq .
List a subdirectory by appending the path: .../secret/metadata/<prefix>/.
Delete a secret
curl -s -X DELETE http://127.0.0.1:8200/v1/secret/data/<path> \
-H "X-Vault-Token: openrig-dev-token"
Explaining Secrets
When asked to explain the current secret structure, list all paths and summarize what each contains. Use the list endpoint recursively if needed.
Important Notes
- This is Vault dev mode — all data is in-memory and lost on restart
- The KV secrets engine is mounted at
secret/by default in dev mode - Use the
rig env statuscommand to verify Vault health through OpenRig before direct probing
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |