Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
CLI tool that stores API keys in GNOME Keyring via libsecret and syncs them to OpenClaw config files and the systemd user environment. Supports keys for OpenAI, Gemini, Discord, GIPHY, Google Places, LinkedIn, and Ollama. Restarts the OpenClaw Gateway inside a Distrobox container after updates.
Keeps credentials in the OS keyring rather than plaintext config files, reducing the risk of accidental exposure via dotfiles or version control.
When to use it
- Storing an OpenAI API key without hardcoding it in config files
- Rotating a Discord bot token across all OpenClaw services at once
- Listing all currently configured API keys from the command line
- Setting up a fresh OpenClaw installation with all required credentials
- Propagating a new Gemini API key to the running gateway without manual restarts
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: add my OpenAI API key to OpenClaw
- 1Run 'secret-manager list' to check existing keys
- 2Run 'secret-manager OPENAI_API_KEY' and prompt user to paste the key
- 3Script stores the key in GNOME Keyring via secret-tool
- 4Script injects the key into auth-profiles.json and propagates it to systemd user environment
- 5Script restarts the OpenClaw Gateway service inside the Distrobox container
OPENAI_API_KEY stored in system keyring and active in the running OpenClaw Gateway
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.