本文へ移動
cccskills
無料GitHub で公開

vault-user

Use when checking the health of this rig's HashiCorp Vault or writing, reading, listing, deleting or explaining its secrets.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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 status command to verify Vault health through OpenRig before direct probing

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,7882026年10月11日 更新

Use when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,7882026年10月11日 更新

Use when a bounded real-world procedure has a deterministic happy path but brownfield, variable, or partially knowable state; when an operation must resume from verified evidence; or when deciding whether agent judgment or ordinary code should own a procedure's control loop.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,7882026年10月11日 更新

Use when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured → named → inspectable → used → promoted → deprecated), provenance honesty, and refusal rules. NOT a VM image; a managed starting point composed from agent role + startup context + optional native session source + provenance.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,7882026年10月11日 更新

Use when designing or auditing how an agent becomes useful after launch — AGENTS.md overlays, role files, skills, rig specs, workflow specs, startup checklists, refocus messages, "rig context" surface. Covers the 4 failure modes that make startup context fail (old rig spec misses current operating mode; current agents never told about new guidance; startup file as dumping ground; orchestrator transmits implementation without preserving product intent).

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,7882026年10月11日 更新

Use before launching a team during agent-guided setup, or when a user asks to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy.

日本語の概要は準備中です。原文の説明を表示しています。

mvschwarz/openrig6,7882026年10月11日 更新

mvschwarz のスキルをすべて見る

このスキルの問題を報告する