Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Add paid tier Stripe integration scaffold; stripe-setup.sh, stripe-checkout.sh, paid tier docs
What This Skill Does
API key manager for OpenClaw. Stores, lists, tests, and deletes keys without exposing them in chat or shell history. Keys are written directly to openclaw.json via gateway config.patch, so any skill with a matching primaryEnv picks them up automatically.
Keys are routed through a macOS secure popup and patched directly into config, so they never appear in chat history, shell logs, or agent output.
When to use it
- Storing an OpenAI key to activate transcription and image generation skills
- Testing a Brave Search key before running a web search
- Listing all configured keys to check which services are set up
- Replacing an expired ElevenLabs key across both voice synthesis and talk features
- Wiring a new third-party API key to a custom skill
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Store my OpenAI API key
- 1Runs store_key_v3.sh targeting the OpenAI config paths
- 2macOS popup appears and user pastes the key into the hidden input field
- 3Script calls gateway config.patch with the key value for all relevant config paths
- 4Gateway restarts and the key takes effect immediately
- 5Agent reports success — key value is never shown in chat
OpenAI key is active and available to all skills that declare OPENAI_API_KEY as their primaryEnv