bitwarden

What This Skill Does

The bitwarden skill provides a robust interface for interacting with the Bitwarden CLI (bw). It allows an AI agent to securely manage credentials, generate strong passwords, and retrieve secrets from a Bitwarden or Vaultwarden vault. By utilizing a dedicated tmux session, the skill maintains an active, authenticated environment through the BW_SESSION environment variable, ensuring that sensitive operations remain persistent and secure throughout the agent's task lifecycle.

Installation

To install this skill, use the OpenClaw CLI command: clawhub install openclaw/skills/skills/jimihford/openclaw-bitwarden. Ensure that the Bitwarden CLI (bw) is installed and available in your system path. For development or testing environments, it is recommended to spin up a local instance of Vaultwarden using the provided Docker Compose files, which offers a lightweight, compatible backend for your vault data.

Use Cases

This skill is designed for automation scenarios where secrets are required to perform secondary tasks. Common use cases include: securely fetching API keys for cloud providers, retrieving database passwords for automated migrations, generating high-entropy passwords for new service sign-ups, and auto-filling multi-factor authentication (TOTP) codes via the CLI. It is an essential tool for any agent that needs to authenticate with third-party services on behalf of the user without hardcoding credentials.

Example Prompts

1. "Unlock my vault and retrieve the GitHub API token so I can push these changes."
2. "Generate a 32-character secure password for the new production database service and save it as a new item in my vault."
3. "Sync the Bitwarden vault and find the TOTP code for my AWS root account."

Tips & Limitations

Always prioritize security by avoiding the logging of secret values. The skill uses bw get password for targeted retrieval to minimize the exposure of full JSON item dumps. Remember that the vault locks automatically for security; if you receive a 'Vault is locked' error, simply trigger the unlock workflow again. For production environments, ensure your tmux sockets are restricted to user-level permissions to prevent unauthorized access to the active session key.