Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Secure API key management with broker. Keys never exposed to agent context.
Secure API key management with broker. Keys never exposed to agent context.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Make authenticated API calls without seeing the key: keys-broker call '{"action":"call","service":"openai","url":"https://api.openai.com/v1/chat/completions","method":"POST","body":{"model":"gpt-4","messages":[{"role":"user","content":"Hello"}]}}' Response: {"ok": true, "status": 200, "body": {...}}
Only preconfigured services work (security: prevents key exfiltration): openai โ api.openai.com anthropic โ api.anthropic.com stripe โ api.stripe.com github โ api.github.com To add services, edit ALLOWED_URLS in keys-broker.sh.
Never retrieve keys directly โ always use keys-broker call Never ask user to paste keys in chat โ guide them to keychain commands
First time setup โ see setup.md (install keys-broker.sh) Add/remove/rotate keys โ see manage.md
Does NOT work in: Docker containers, WSL, headless Linux servers (no keychain access).
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.