secret-manager
par jswortz
Coding Agents & IDEsRésumé
Manage API keys securely via GNOME Keyring and inject them into OpenClaw config.
Description
Ce que fait ce skill
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.
Quand l'utiliser
- 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
Exemple de workflow
User asks: add my OpenAI API key to OpenClaw
- 1
Run 'secret-manager list' to check existing keys
- 2
Run 'secret-manager OPENAI_API_KEY' and prompt user to paste the key
- 3
Script stores the key in GNOME Keyring via secret-tool
- 4
Script injects the key into auth-profiles.json and propagates it to systemd user environment
- 5
Script restarts the OpenClaw Gateway service inside the Distrobox container
OPENAI_API_KEY stored in system keyring and active in the running OpenClaw Gateway
Prérequis
- libsecret-tools system package (apt install libsecret-tools / dnf install libsecret / pacman -S libsecret)
- API keys for each service to be configured (e.g. OPENAI_API_KEY, GEMINI_API_KEY, DISCORD_BOT_TOKEN)
- GNOME Keyring running (standard on GNOME-based Linux desktops)
Installation
clawhub install jswortz/secret-managerExécute la commande CLI, ou colle l'instruction dans Claude Code, Cursor, Codex ou l'agent de code que tu utilises.